I'm playing around with the use of a Jira Issue Collector so that users in my organization without Jira access can submit bugs and they'll come right into my backlog.
My questions are:
Hello @Jodi Jones
1. Since you said the users of the issue collector don't have Jira access, I am guessing the the issue collector setting for Match Reporter is set to Always use Issue Reporter, which means the Jira issues created by the issue collector have a static reporter that is not the person who actually submitted the form. In that case Jira notifications based on the Reporter field would not be sent to the person who submitted the form.
If, within the form, you collect the email address of the submitter, then you could use an Automation Rule to send the submitter a confirmation.
3. So far I have not found any field or property that indicates an issue was created as the result of an Issue Collector submission. If you had a special user that you used only as the Reporter for the Issue Collector issues, then you could use that as a way to identify the issues created from the Collector.
2. The creation of an issue by the Collector triggers the Issue Created Event. So whatever Notifications you have based on that event will be fired.
If you want special notifications for issues created by the Collector, you could set up an Automation Rule that would be triggered by Issue Created, and use a Condition to detect that the issue was created by the Collector (see #3 above), and then use the Send Email action to email the interested parties.
4. Is your question here focused on the timing ("immediately") or the addition of the issue specifically to the "backlog"?
If it is the latter, Issue Collectors can be used only with Company Managed projects. The definition of "backlog" is based on the Agile Board(s) you have referencing that project. If you are using Scrum boards, then yes, the issue would appear in the Backlog for any Scrum board where the newly created issue is within scope. For Kanban boards the "backlog" is based on the Status of the issues, so the issue would appear in the Backlog for Kanban boards where the newly created issue is within the board's scope and the Status of the newly created issue is mapped to the Backlog for the Kanban board.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.