NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      The Request Participant Field When added to the create issue Screen does not populate on the screen

      Environment

      • (Cloud) JIRA Service Desk v3.0.0-OD-04-002-D20150924T014602
      • (Cloud) JIRA Service Desk Application v3.3.0-OD-1000.663.0
      • JIRA v1000.571.2

      Steps to Reproduce

      1. Add Request Participant to the Create issue Screen on Service Desk Project
      2. Logged in as an agent, select Create issue

      Expected Results

      Request Participant Field is present on Create issue Screen

      Actual Results

      • Request Participant Field acts like a hidden field
      • Wheres My Field? Helper indicates the field is present on the screen

      Workaround

      • Set Request Participant to the edit issue Screen
      • Create issue without a Request Participant
      • Edit issue and add in a Request Participant value

      Notes:

      The same thing also happens for the Organization field.

            [JSDSERVER-2428] Request Participant Missing from Create issue Screen

            I dont understand how the cloud based product can be so far behind the server based. Is the code base that different?

            Benjamin Peikes added a comment - I dont understand how the cloud based product can be so far behind the server based. Is the code base that different?

            bpeikes

            You'll want to check out the corresponding cloud ticket http://jira.atlassian.com/browse/JSDCLOUD-2428 .

            Looks like they've changed it to a suggestion and are tracking it here https://jira.atlassian.com/browse/JSDCLOUD-1511

            Lachlan G (Inactive) added a comment - bpeikes You'll want to check out the corresponding cloud ticket http://jira.atlassian.com/browse/JSDCLOUD-2428  . Looks like they've changed it to a suggestion and are tracking it here https://jira.atlassian.com/browse/JSDCLOUD-1511

            Any idea when this will be fixed in cloud version?

            Benjamin Peikes added a comment - Any idea when this will be fixed in cloud version?

            Hi,

            from version 4.3 of plugin Extension for JIRA Service Desk there is Request Participants Custom field and it edits request participants of issue. You can use it on create, edit and transition screen also on creation screen on customer portal. Here you can find more information: https://intenso.atlassian.net/wiki/display/SPFJSD/Request+Participants+Custom+field

            Best Regards

            Daniel Bajrak added a comment - Hi, from version 4.3 of plugin Extension for JIRA Service Desk there is Request Participants Custom field and it edits request participants of issue. You can use it on create, edit and transition screen also on creation screen on customer portal. Here you can find more information: https://intenso.atlassian.net/wiki/display/SPFJSD/Request+Participants+Custom+field Best Regards

            Agreed. Its not clear why some fields have special treatment.

            Benjamin Peikes added a comment - Agreed. Its not clear why some fields have special treatment.

            roymeo added a comment -

            I'm not sure why either this or JSD-1511 hasn't been closed as a duplicate of the other.

            roymeo added a comment - I'm not sure why either this or JSD-1511 hasn't been closed as a duplicate of the other.

            Y Rossi added a comment -

            This would be a great feature to have as often we want to create a ticket and straight away inform everyone who was involved in the initial discussions. the same goes for watchers.

            Y Rossi added a comment - This would be a great feature to have as often we want to create a ticket and straight away inform everyone who was involved in the initial discussions. the same goes for watchers.

            I wish this feature gets included in upcoming builds

            jennie jennie added a comment - I wish this feature gets included in upcoming builds

            PL.IS added a comment -

            I also agree that this field should be visible during creation of new issue Service Desk. Without this field we duplicate some actions, we need to go to created tickets and this participant users which generate more clicks

            PL.IS added a comment - I also agree that this field should be visible during creation of new issue Service Desk. Without this field we duplicate some actions, we need to go to created tickets and this participant users which generate more clicks

            That's something we absolutely need in our Service Desks.
            The feature is particulary useful when we ask customers to copy their supervisor, safety controlers, the laboratory manager, etc. in the request form.
            Definitely wanted.

            Malysa Martin added a comment - That's something we absolutely need in our Service Desks. The feature is particulary useful when we ask customers to copy their supervisor, safety controlers, the laboratory manager, etc. in the request form. Definitely wanted.

              lgoodhewcook Lachlan G (Inactive)
              emccutcheon Earl McCutcheon
              Affected customers:
              60 This affects my team
              Watchers:
              49 Start watching this issue

                Created:
                Updated:
                Resolved: