We are planning to use Jira to track bugs and enhancements as part of our product development. Our process as we have it mapped out has a the "customer friendly" documentation as a custom field on the Jira issue. What are some methods for exposing this documentation to customers without showing them all of the other "internal stuff" that is part of the Jira issue?
One thought we had was to extract these fields from the Jira issue and place them within the body of a confluence page? Is there a macro to expose just a custom field's contents within a confluence page without all of the other information?
Does anybody do something similar or have other methods of creating customer documentation on the Jira issue level?
If you are using the JIRA Service Desk plugin for example, you have the ability of linking one specific Service Desk to a Confluence space. So if you gather all the "Customer documents" in one space (in Confluence) and the internal documentation in another space, you can simply create a service desk and then link the service desk to the customer documents space.
By doing this, every time the customer access JIRA to report a problem/create an issue, they will have the possibility of also browsing through your documentation without accessing other Confluence spaces.
Please notice that you will need to set permissions per space in Confluence as well, otherwise the customer will be linked to the correct space in confluence but will have the ability to access other spaces once they are in Confluence.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot