Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-4736

Default value for multi user picker field is not rendered correctly

      Steps to reproduce:

      1. Add a custom field (multi user picker) in JIRA, with some default values (add some users)
      2. Add this filed inside cards configuration
      3. Create a new card. The field is rendered incorrectly in the card creation screen

          Form Name

            [JSWSERVER-4736] Default value for multi user picker field is not rendered correctly

            Fixed as part of GHS-6883

            Michael Ruflin (Inactive) added a comment - Fixed as part of GHS-6883

            Great, I'll try it out in the Rapid Board as soon as we get a usable version in OnDemand (hopefully a near-term update). As long as I can add the notifications field to the 'New Issue' page in the Rapid Board (I presume this is configurable), and the notification field has the defaults I've configured we'll be in perfect shape.

            Regarding improving the Watcher field functionality, there are very long running JIRA issues open on the subject, with hundreds of votes and comments, I've added mine of course. There are plugins that will enable some more advanced use cases, but nothing in the product or available to OnDemand customers. It's my #1 complaint, basecamp has JIRA whipped on this one puny little point.

            David Parks added a comment - Great, I'll try it out in the Rapid Board as soon as we get a usable version in OnDemand (hopefully a near-term update). As long as I can add the notifications field to the 'New Issue' page in the Rapid Board (I presume this is configurable), and the notification field has the defaults I've configured we'll be in perfect shape. Regarding improving the Watcher field functionality, there are very long running JIRA issues open on the subject, with hundreds of votes and comments, I've added mine of course. There are plugins that will enable some more advanced use cases, but nothing in the product or available to OnDemand customers. It's my #1 complaint, basecamp has JIRA whipped on this one puny little point.

            In the Rapid Board the 'new issue' dialog is the JIRA quick create dialog and the JIRA quick edit dialog can be easily opened with the 'e' keyboard shortcut. Both of these methods should be able to render and edit the multi-user picker correctly. We're not specifically planning on addressing the issue watching situation you're describing (though I agree it's an interesting use case). It's probably worth raising the feature request in the JIRA project to see if they plan on implementing it.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - In the Rapid Board the 'new issue' dialog is the JIRA quick create dialog and the JIRA quick edit dialog can be easily opened with the 'e' keyboard shortcut. Both of these methods should be able to render and edit the multi-user picker correctly. We're not specifically planning on addressing the issue watching situation you're describing (though I agree it's an interesting use case). It's probably worth raising the feature request in the JIRA project to see if they plan on implementing it. Thanks, Shaun

            David Parks added a comment - - edited

            I could be ok with that, I'm pretty excited about the prospect of getting a usable RapidBoard in OnDemand sometime soon. I'd love to hear how this is being address (or did I read correctly "will be addressed") in the RapidBoard?

            Our biggest complaint in moving from Basecamp (ick) to JIRA (yippie) is the lack of Basecamps' sole feature that seems to make it successful, that is, the ability to add other users to the notification list on a conversation/ticket/issue/bug/task/etc.

            It's common to sit in a meeting between developers and business-side folk and take an issue (say a GreenHopper technical task, or story) and want the business dude to get some notifications of its progress and comments. But we would look like fools to have to email a JIRA link to the guy and say "Hey, click on this link and 'watch' the task so you get updates". We just want to add him ourselves and let him receive the updates. This is exactly what we had managed to get configured using the User Picker field and a custom Notifications scheme, before it broke recently of course.

            We certainly hope that the RapidBoard addresses this simple requirement in a fluid way.

            David Parks added a comment - - edited I could be ok with that, I'm pretty excited about the prospect of getting a usable RapidBoard in OnDemand sometime soon. I'd love to hear how this is being address (or did I read correctly "will be addressed") in the RapidBoard? Our biggest complaint in moving from Basecamp (ick) to JIRA (yippie) is the lack of Basecamps' sole feature that seems to make it successful, that is, the ability to add other users to the notification list on a conversation/ticket/issue/bug/task/etc. It's common to sit in a meeting between developers and business-side folk and take an issue (say a GreenHopper technical task, or story) and want the business dude to get some notifications of its progress and comments. But we would look like fools to have to email a JIRA link to the guy and say "Hey, click on this link and 'watch' the task so you get updates". We just want to add him ourselves and let him receive the updates. This is exactly what we had managed to get configured using the User Picker field and a custom Notifications scheme, before it broke recently of course. We certainly hope that the RapidBoard addresses this simple requirement in a fluid way.

            As we are focusing on replacing this functionality in the Rapid Board we will not be correcting this bug.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - As we are focusing on replacing this functionality in the Rapid Board we will not be correcting this bug. Thanks, Shaun

            mkurz added a comment -

            I can confirm this bug.
            The default values are displayed like "com.atlassian.crowd.embedded.ofbiz.OfBizUser@xxxxx".

            mkurz added a comment - I can confirm this bug. The default values are displayed like "com.atlassian.crowd.embedded.ofbiz.OfBizUser@xxxxx".

              Unassigned Unassigned
              amohdaris Azwandi Mohd Aris (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: