We are testing JIRA Service Desk Cloud for our service desk, we are currently using ServiceNow and want to migrate some process that are automated and have custom fields/forms.
Screen Shot 2016-03-09 at 6.55.41 PM.png
JIRA requires a summary as it is used everywhere to give users a brief idea of what the issue is about.
Your screenshot says things to me that make me want to suggest that instead of having a "survey id", you should ask the user for the survey id as the summary of the issue (for that request type only). Saves you a field and solves the summary problem.
For this particular use case you are correct, but I'm not sure if it's a good workaround for all use cases we have specially because the Summary field label can't be changed to say "Survey ID" or whatever field I need (If it's a text field).
Thanks for the suggestion!
It's a bit of a cheat as I've done something similar in the past - on Server, you have the flexibility to install something that will take the summary and copy it over into the "survey id" and then set the summary to something a bit more informative (like "Survey id is: xxxxx"). You still need the summary populated, but as it echoes the custom field, it looks a lot better.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs