JT-50850: Inspection/code-assist not identifying object properties when JSDoc type is multiple (piped)

December 15, 2018, 2:27 pm

≫ Next: JT-50851: Strange display of adjacent blockquotes (2 closely related issues)

≪ Previous: JT-50849: Document what "duplicate" means

$

0

0

Reporter	Steve Larsen (slarsen)
Created	Dec 16, 2018 1:27:05 AM
Updated	Dec 16, 2018 1:27:05 AM
State	Submitted
Assignee	Unassigned
Subsystem	No Subsystem
Type	Bug
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	Unscheduled
Affected versions	Unknown

This is PHPStorm version 2018.3.

The code using a JSDoc comment where the type is identified as multiples (piped) -- e.g. @param {Object1|Object2} myparam, shows properties of the object as unidentified. When the multiple types is removed for a single type -- e.g. @param {Object1} myparam, then the properties of the object are identified correctly.

Example 1 - When multiple objects are defined for JSDoc param type:
Note when the model object is identified as multiple types, show the properties of the model (e.g. id and idAttribute), as unidentified...

Example 2 - When only a single object is defined for JSDoc param type:
Note when the model object is identified as a single type, show the properties of the model (e.g. id and idAttribute) as identified correctly.

Example 3 - Code assist works when multiple object types:
This is fascinating that while the properties are unidentified to Inspection, code assist clearly shows them...

---

JT-50851: Strange display of adjacent blockquotes (2 closely related issues)

December 16, 2018, 1:55 pm

≫ Next: JT-49477: Collapse text changes in an Expand mode in an activity stream

≪ Previous: JT-50850: Inspection/code-assist not identifying object properties when JSDoc type is multiple (piped)

$

0

0

Reporter	Solomon Ucko (dhDZsG9QfQK3VTiF5KOs)
Created	Dec 17, 2018 12:55:20 AM
Updated	Dec 17, 2018 12:55:55 AM
State	Submitted
Assignee	Unassigned
Subsystem	Markdown
Type	Bug
Priority	Normal
Browser	Chrome
OS	Windows 7
Fix versions	Unscheduled
Affected versions	2018.3

In the (generated?) CSS:

.wiki.common-markdown blockquote {
  border-left: 2px solid #b8d1e5;
  border-left: 2px solid var(--ring-icon-color);
  padding-left: 1em;
  margin: 0; /* Causes issue #1 */
  display: inline-block; /* Causes issue #2 */
}

Issue #1 (120 total printables in the result):

Blockquotes are displayed with margin: 0;, causing them to display as a single, contiguous blockquote. (They should be 2 separate blockquotes in this case to allow for both options to be chosen; see https://spec.commonmark.org/0.28/#example-205.)

Markdown:

> 1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678

> 0

HTML:

<blockquote>
<p>0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567</p>
</blockquote>
<blockquote>
<p>0</p>
</blockquote>

Result:

01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678

0

Issue #2 (119 total printables in the result):

Adjacent blockquotes that are short enough to be displayed on the same line are, due to the display: inline-block;. (They should be displayed on 2 separate lines; this just looks weird.)

Markdown:

> 0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567

> 0

HTML:

<blockquote>
<p>0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567</p>
</blockquote>
<blockquote>
<p>0</p>
</blockquote>

Result:

0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567

0

JT-49477: Collapse text changes in an Expand mode in an activity stream

December 16, 2018, 11:20 pm

≫ Next: JT-49655: Always collapse text changes

≪ Previous: JT-50851: Strange display of adjacent blockquotes (2 closely related issues)

$

0

0

Reporter	Alexander Anisimov (xi-eye)
Created	Oct 1, 2018 5:16:29 PM
Updated	Dec 17, 2018 10:20:23 AM
State	Open
Assignee	Alexander Anisimov (xi-eye)
Subsystem	No Subsystem
Type	Task
Priority	Normal
Fix versions	Unscheduled

Details should be always collapsed

JT-49655: Always collapse text changes

December 16, 2018, 11:20 pm

≫ Next: JT-23802: monospaced font for the issue description

≪ Previous: JT-49477: Collapse text changes in an Expand mode in an activity stream

$

0

0

Reporter	Alexander Anisimov (xi-eye)
Created	Oct 11, 2018 12:05:21 PM
Updated	Dec 17, 2018 10:20:45 AM
State	Open
Assignee	Unassigned
Subsystem	No Subsystem
Type	Task
Priority	Normal
Fix versions	Unscheduled

Details should be always collapsed

JT-23802: monospaced font for the issue description

December 16, 2018, 11:57 pm

≫ Next: JT-48502: Support connections from YouTrack Standalone installations to YouTrack App for Slack

≪ Previous: JT-49655: Always collapse text changes

$

0

0

Reporter	Daniil Vodopian (Daniil.Vodopian)
Created	Feb 25, 2014 1:28:43 AM
Updated	Dec 17, 2018 10:57:55 AM
State	Open
Assignee	Ekaterina Zaikina (Ekaterina_Zaikina)
Subsystem	Wiki
Type	Usability Problem
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	Unscheduled
Affected versions	Unknown

I often write code in the description field of an issue, but the font here is NOT monospaced.

That causes troubles with alignment:

// Aligned in the description text
val map = mapOf(1 to 2,
                              3 to 4,
                              5 to 6)

// Aligned in the resulting page
val map = mapOf(1 to 2,
                3 to 4,
                5 to 6)

I hope there is a simple fix for this annoying problem.

JT-48502: Support connections from YouTrack Standalone installations to YouTrack App for Slack

December 17, 2018, 2:23 am

≫ Next: JT-50840: Saved search does not send notifications

≪ Previous: JT-23802: monospaced font for the issue description

$

0

0

Reporter	Scott Adams (Scott.Adams)
Created	Jul 31, 2018 1:31:27 PM
Updated	Dec 17, 2018 1:23:44 PM
State	Open
Assignee	Unassigned
Subsystem	Konnector App
Type	Feature
Priority	Normal
Fix versions	Unscheduled

JT-50840: Saved search does not send notifications

December 17, 2018, 3:11 am

≫ Next: JT-50853: Can't display attached images with spaces in file names in comments

≪ Previous: JT-48502: Support connections from YouTrack Standalone installations to YouTrack App for Slack

$

0

0

Reporter	Arseniy Nisnevich (Arseniy.Nisnevich)
Created	Dec 14, 2018 1:48:06 PM
Updated	Dec 17, 2018 2:11:22 PM
State	Open
Assignee	Anastasia Bartasheva (ana.bartasheva)
Subsystem	Notifications
Type	Support Request
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	Unscheduled
Affected versions	Unknown

Here is my saved search: https://youtrack.jetbrains.com/issues/IDEA?q=Assignee:%20PlatformUI . I made it public for the purpose of this issue, so you can find it in the list of saved searches if you wish.

Here are notification settings of my saved search:

Actual result: I do not receive notifications (tested for two days, while about 20 tickets were created in this search). Email box works well, I receive notifications about tickets I am watcher of. Checked spam as well.

JT-50853: Can't display attached images with spaces in file names in comments

December 17, 2018, 3:27 am

≫ Next: JT-31774: Add integration for self-hosted Bitbucket

≪ Previous: JT-50840: Saved search does not send notifications

$

0

0

Reporter	Nikolaj Schumacher (nschum)
Created	Dec 17, 2018 1:44:08 PM
Updated	Dec 17, 2018 2:27:51 PM
Resolved	Dec 17, 2018 2:27:39 PM
State	Duplicate
Assignee	Unassigned
Subsystem	No Subsystem
Type	Bug
Priority	Normal
Browser	Safari
OS	Any OS
Fix versions	Unscheduled
Affected versions	Unknown

When writing a comment, I can't show an attached image if it has spaces in its file name, e.g.:
![screenshot](Screen Shot 2018-11-26 at 22.30.06.png)

expected: The attached image is shown in comment preview
actual: The text above is shown verbatim in comment preview

It seems to work correctly in the issue description preview.

---

JT-31774: Add integration for self-hosted Bitbucket

December 17, 2018, 3:48 am

≫ Next: JT-49062: Performance problem at custom fields with many values

≪ Previous: JT-50853: Can't display attached images with spaces in file names in comments

$

0

0

Reporter	Burhan Khalid (burhan)
Created	Sep 2, 2015 1:06:22 PM
Updated	Dec 17, 2018 2:48:49 PM
State	Open
Assignee	Alexander Volfman (Alexander.Volfman)
Subsystem	Bitbucket Integration
Type	Feature
Priority	Normal
Fix versions	Unscheduled

Please add the ability to integrate with self-hosted VCS systems; for example stash (bitbucket).

JT-49062: Performance problem at custom fields with many values

December 17, 2018, 3:49 am

≫ Next: JT-48616: Fix the wording for private field settings in the global fields list

≪ Previous: JT-31774: Add integration for self-hosted Bitbucket

$

0

0

Reporter	Stefan Sidlo (ssdcops)
Created	Sep 6, 2018 4:35:37 PM
Updated	Dec 17, 2018 2:49:16 PM
Resolved	Nov 16, 2018 6:44:34 PM
State	Fixed
Assignee	Roman Kolobov (rekolobov)
Subsystem	Custom Fields
Type	Performance Problem
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	2018.3
Affected versions	Unknown

Hey,

We have 2 custom fields which have close to 7000 values.
Both fields suffer heavy performance problems if you try to enter a value.
They are both Enum-Type Custom Fields.

If you try to enter a character, it tries to filter the whole drop-down.
The more you enter, the faster it gets.

JT-48616: Fix the wording for private field settings in the global fields list

December 17, 2018, 3:53 am

≫ Next: JT-49375: Can't make independent copy of required field values

≪ Previous: JT-49062: Performance problem at custom fields with many values

$

0

0

Reporter	Scott Adams (Scott.Adams)
Created	Aug 7, 2018 6:17:41 PM
Updated	Dec 17, 2018 2:53:55 PM
Resolved	Sep 29, 2018 6:09:43 PM
State	Verified
Assignee	Evgeny Naumenko (jk)
Subsystem	Custom Fields
Type	Task
Priority	Normal
Fix versions	2018.3.46358

The hint text is out of date. I have a few suggestions:

1. Just remove it. As it stands now, the setting only determines the initial default when the field is attached to a project. Anybody who really needs to know more about it can read the documentation.
2. Change to: Restricts vibisility to users with "Read Issue Private Fields" and updates to users with "Update Issue Private Fields". At the global level, this setting determines the initial default when the field is attached to a project. Exiting projects to which the field is already attached are not affected.
3. Use a shorter version of option 2 with a "Learn more" link.

I leave it up to you to choose how you want to fix the issue. If you want to go with option 3, I can provide a target page for the link.

JT-49375: Can't make independent copy of required field values

December 17, 2018, 3:56 am

≫ Next: JT-49415: Card is not shown if user can't update field

≪ Previous: JT-48616: Fix the wording for private field settings in the global fields list

$

0

0

Reporter	Ekaterina Alekseeva (Ekaterina.Alekseeva)
Created	Sep 25, 2018 1:43:49 PM
Updated	Dec 17, 2018 2:56:52 PM
Resolved	Nov 28, 2018 5:50:57 PM
State	Verified
Assignee	Leonid Stryuk (Leonid.Stryuk)
Subsystem	Custom Fields
Type	Bug
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	Unscheduled
Affected versions	Unknown

build 45906

STR:

1. Create required CF which use some existing bundle of values (or merge its bundle with set of values of some other field)
2. Try to make independent copy

AR:
Error "Failed to attach field to bundle. Can't move field to selected bundle"

JT-49415: Card is not shown if user can't update field

December 17, 2018, 4:01 am

≫ Next: JT-44318: Desc sorting for version type custom fields

≪ Previous: JT-49375: Can't make independent copy of required field values

$

0

0

Reporter	Ekaterina Alekseeva (Ekaterina.Alekseeva)
Created	Sep 27, 2018 3:18:21 PM
Updated	Dec 17, 2018 3:01:37 PM
Resolved	Nov 14, 2018 1:03:32 PM
State	Verified
Assignee	Daria Vasina (daria.vasina)
Subsystem	Custom Fields
Type	Bug
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	Unscheduled
Affected versions	Unknown

build 46009

Hover username in custom field which current user cannot update

AR:
Card is not shown

JT-44318: Desc sorting for version type custom fields

December 17, 2018, 4:05 am

≫ Next: JT-50388: GET Response Project Custom Fields

≪ Previous: JT-49415: Card is not shown if user can't update field

$

0

0

Reporter	Irina Karpova (irinavp)
Created	Nov 9, 2017 11:01:48 AM
Updated	Dec 17, 2018 3:05:08 PM
Resolved	Oct 22, 2018 6:39:14 PM
State	Verified
Assignee	Anna Zhdan (Anna.Zhdan)
Subsystem	Custom Fields
Type	Feature
Priority	Normal
Fix versions	2018.3

Hello,

It would be great to have desc sorting for version type fields (or any other type as well).

What steps will reproduce the problem?

1. Open Edit Project;
   
2. Go to Fields tab;
   
3. Choose version type field;
   
4. Press "Edit for all affected project button";
   
5. Choose from drop down field "Sort by".

What is the expected result?
It should have an option to sort values in descending order for both: by name and by release date.
And this chosen sorting type should affect the list of versions on issue creation/edit, when version added from there.

What happens instead?
There is only an option to sort values in ascending order for both: by name and by release date.

For my team it would be very helpful, because every time when team member adds version from issue, it appears at the bottom of a list, and
our youtrack administrator has to move it up manually on project edit. Thank you.

JT-50388: GET Response Project Custom Fields

December 17, 2018, 4:10 am

≫ Next: JT-44466: Check that value for inaccessible field was not set

≪ Previous: JT-44318: Desc sorting for version type custom fields

$

0

0

Reporter	Dmitrijs Nikitenko (dmitrijn)
Created	Nov 20, 2018 5:58:19 PM
Updated	Dec 17, 2018 3:10:11 PM
Resolved	Nov 21, 2018 3:11:37 PM
State	Verified
Assignee	Leonid Stryuk (Leonid.Stryuk)
Subsystem	Custom Fields
Type	Bug
Priority	Normal
Browser	Any Browser
OS	Any OS
Fix versions	2018.3.47965
Affected versions	2018.3.47247, 2018.3.47109, 2018.3.47078, 2018.3.47010

What steps will reproduce the problem?

1. https://www.jetbrains.com/help/youtrack/incloud/GET-Project-Custom-Fields.html
2. Why default tags are changed when you receive REST API GET response?
3. Last working version with tags defined in documentation is - #Build 46727
4. Some integration dependency packages from 3rd party apps are not working anymore with newest tags.

What is the expected result?
Must be (working version #Build 46727):

<projectCustomFieldRefs>
</projectCustomFieldRefs>

With newer version it's differs:

<projectCustomFieldBeanRefs>
</projectCustomFieldBeanRefs>

What happens instead?
Can't receive REST API GET response tags that are predefined in documentation

---

JT-44466: Check that value for inaccessible field was not set

December 17, 2018, 4:14 am

≫ Next: JT-47637: New type, project field,...

≪ Previous: JT-50388: GET Response Project Custom Fields

$

0

0

Reporter	Anna Zhdan (Anna.Zhdan)
Created	Nov 20, 2017 5:11:25 PM
Updated	Dec 17, 2018 3:14:46 PM
Resolved	Nov 21, 2017 3:10:29 PM
State	Verified
Assignee	Anna Zhdan (Anna.Zhdan)
Subsystem	Custom Fields
Type	Task
Priority	Normal
Fix versions	Unscheduled

add it to Issue's beforeWorkflow

JT-47637: New type, project field,...

December 17, 2018, 4:16 am

≫ Next: JT-47642: String -> Text field converter

≪ Previous: JT-44466: Check that value for inaccessible field was not set

$

0

0

Reporter	Anna Zhdan (Anna.Zhdan)
Created	Jun 13, 2018 5:46:58 PM
Updated	Dec 17, 2018 3:16:13 PM
Resolved	Jun 17, 2018 1:09:01 PM
State	Verified
Assignee	Anna Zhdan (Anna.Zhdan)
Subsystem	Custom Fields
Type	Task
Priority	Normal
Fix versions	Unscheduled

JT-47642: String -> Text field converter

December 17, 2018, 4:18 am

≫ Next: JT-47639: Checkboxes support

≪ Previous: JT-47637: New type, project field,...

$

0

0

Reporter	Anna Zhdan (Anna.Zhdan)
Created	Jun 13, 2018 5:48:01 PM
Updated	Dec 17, 2018 3:18:06 PM
Resolved	Jun 19, 2018 12:12:00 PM
State	Verified
Assignee	Anna Zhdan (Anna.Zhdan)
Subsystem	Custom Fields
Type	Task
Priority	Normal
Fix versions	Unscheduled

JT-47639: Checkboxes support

December 17, 2018, 4:19 am

≫ Next: JT-6170: Custom field type with wiki content

≪ Previous: JT-47642: String -> Text field converter

$

0

0

Reporter	Anna Zhdan (Anna.Zhdan)
Created	Jun 13, 2018 5:47:14 PM
Updated	Dec 17, 2018 3:19:17 PM
Resolved	Jun 19, 2018 12:57:35 PM
State	Verified
Assignee	Leonid Stryuk (Leonid.Stryuk)
Subsystem	Custom Fields
Type	Task
Priority	Normal
Fix versions	Unscheduled

JT-6170: Custom field type with wiki content

December 17, 2018, 4:21 am

≫ Next: JT-50854: Use fixed notifications amount per pack to ensure memory limit

≪ Previous: JT-47639: Checkboxes support

$

0

0

Reporter	Vadim Gurov (vgurov)
Created	Jun 4, 2010 2:47:38 PM
Updated	Dec 17, 2018 3:21:02 PM
Resolved	Aug 15, 2018 10:21:31 AM
State	Verified
Assignee	Anna Zhdan (Anna.Zhdan)
Subsystem	Custom Fields
Type	Feature
Priority	Normal
Fix versions	2018.3.46358