Let’s look at how to use the Issue Collector. In this example, the issue collector allows you to manage that feedback internally. You could also embed this into functionality into any website and use it to gather feedback or bug reports. 3: Collecting user feedback and bug reports from an external web site That project has to be completely unavailable to people who are not members of the finance team. They do not, however, have access to the Finance project. This use case is the same as the first example, but users do have access to Jira. 2: Users do not have access to the Finance project This is the example we have discussed in the Issue Collector for Server post. People with access to Confluence create the expense claim and the Finance team would like you to create an issue to that they can manage your expense claim. In this example, the trigger tab is embedded in the Finance space in Confluence. In this case, and if you were using Confluence Server, an example could be for managing internal processes, specifically managing expense claims. It could be the case that you have users with access to Confluence but not to Jira. When clicked, this prompts the user to fill in a form which creates an issue in Jira. The issue collector allows you to embed a trigger tab into any website. An often looked over feature of Jira is the Issue Collector. In the run-up to the event, we’re going to publish a series of blog posts focusing on using Jira and Confluence together. This year, at Atlassian Summit 2019 in Las Vegas, our very own Dave Gee is running the newly titled official Atlassian University Jira and Confluence Together course.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |