nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue Collector not displaying Issue Key on Feedback message.

Marti Phillips

The organization that I work for currently uses JIRAs Issue Collector to allow non-JIRA users to submit maintenance requests to our facility services department. The unfortunate problem is that as long as the person submitting the ticket is not currently logged into JIRA, the feedback message does not contain the Issue key. That's one of the things that we would like to have in place, but I am unsure how to go about doing that. This issue has been noted on both our development server and our production server. Please let me know if I need to supply additional information.

JIRA Version: 6.4.7

JIRA-DEV Version: 6.3.15

Accepted answers

Marti Phillips

After contacting Atlassian directly about the issue, we were able to find a solution by getting the "JIRA Email This Issue" add-on and configuring that to email the user who submitted the issue with the details of the issue and an issue-key.

All comments

unknown

I guess that the Issue Collector is designed like that. It would make no sense to include the issue key if the reporter won't be able to access that.

We experienced the same issue, what I did was to customize our issue collector so that we can capture an email address and an ID in the issue collector.

Send an email to the the email address field for notifications
If applicable, create an ID from the ID field so that the user can access the ticket

Marti Phillips

Bradley_nmdacr

Actually this makes no Sense at all. What does it matter if the person has the issue key (at least if they reach out to have it tracked they can then provide it). I know several "Issue Collector" style intakes that provide you a "Confirmation Number" doesn't mean I have access to their Project or even their systems. This is honestly a bad and almost lazy decision to not have it capable of providing a Ticket, Story, Feature, or some form of tracible confirmation number to the person submitting the item, without the use of a "add-on".

I mean why not take away 1 item you know everyone will want, make it an "Add-on" and then charge for it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

issue-collector