-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
Severity 3 - Minor
-
36
-
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? 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
- Add Request Participant to the Create issue Screen on Service Desk Project
- 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.
- is related to
-
-
- Closed
-
-
JSDCLOUD-1511 Allow adding Request Participant field into Request Form in Customer Portal
- Under Consideration
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-2428] Request Participant Missing from Create issue Screen
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. 
jennie jennie
added a comment - I wish this feature gets included in upcoming builds 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.
Haddon Fisher
added a comment - Hi mmcmahon, I understand that this functionality wasn't within original scope, and while I'm not sure why (if it looks like a field and acts like a field, why not show it on the screen like any other field?) I won't debate that. However, in that case can the "Where is my field" and\or documentation be updated to let people know that this isn't a normal field?
Haddon Fisher
added a comment - Hi mmcmahon , I understand that this functionality wasn't within original scope, and while I'm not sure why (if it looks like a field and acts like a field, why not show it on the screen like any other field?) I won't debate that. However, in that case can the "Where is my field" and\or documentation be updated to let people know that this isn't a normal field? Hi emccutcheon
This feature was not within the original scope of Request Participants.
We acknowledge that it would be desirable for it to be possible to include in a Create Issue Screen, however, as it is not a bug with existing functionality, I will move to a Suggestion and encourage users to vote for the issue.
Regards
Matt
JIRA Service Desk developer
I am now closing this ticket and encourage you all to vote on the linked suggestion ticket: https://jira.atlassian.com/browse/JSDCLOUD-1511
We are aware however that it might be confusing / not intuitive and we'll look into making this information better flagged / explained (cc rreidl vwong@atlassian.com)