I have some custom fields that get populated as an issue is worked on that I would like to display in the customer portal (when reviewing requests), but i don't want the customers to have to view those custom fields (or set values on them) when they're raising the issue... For example, when an issue goes back to the requestor for UAT, the developer would provide a link to the appropriate test environment via a custom field... The customer should not have to interact with that field when raising the issue, but it should be displayed when reviewing the issue when they are doing UAT. (customers can execute UAT transitions, as we're using Actions for Jira Service Desk)
I've tried adding the custom field to the request type, but of course, the customer sees it when raising an issue, and they can set a value. I've also tried hiding the custom field on the request type, however that subsequently hides the field when reviewing issues on the portal.
Jira Service Desk currently doesn't have the ability to do this. We do have an open Feature Request for this type of functionality.
It would be great if you could add your vote to the feature requests, you can feel free to leave a comment with your use case as well which can be used if the feature is chosen for development.
In the meantime, I'm not aware of any plugins that offer this functionality, but there is a huge number of them out there so perhaps someone can chime in with one if it exists.
Thanks for your answer. I've found a bit of a workaround you might consider for other folks with similar needs.
In addition to Service Desk, we're also using Actions for Service Desk, to allow our customers to execute transitions (questions, UAT approval etc.). Using Actions for Jira Service Desk, I can add Read Only fields to transition screens. I've done that, though not 100% what i'd like, it's "close enough".
We're refactoring Service Desks as we prepare to move from our legacy license to Data Center and this is turning out to be a huge problem.
For our travel team we may surface a transition to have a receipt mailed to them or something to help them see some of this data. This is so very less than ideal though.
I managed to find a workaround, you essentially need to add the custom field to a specific project context
Make sure your logged in as Admin
1. Go to jira administration and click on Issues
2. Find your custom field
3. Click on the small cog wheel icon and then on configure
4. Fill out the form, which will comprise of details in relation to Configuration scheme label, Issue types and Context. When you come to option box selection ensure you select "Apply to issues under selected projects", this will add the field to the desired project. click add when done
5. Go back to your projects and under request types>> edit fields, the custom field will be available for you to add to the customer request form.
Hope this helps
You can achieve it using our app Extension for Jira Service Desk. In the Visibility section, select Fields tab. Choose your custom field and switch the toggle Hide for all on. This field is hide for customers, but if agent put something in this field, this information is visible on the request.
I guess that it solves your problem.
Hello Atlassian Community! I'm Teresa, the Product Marketing Manager for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...
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