Issue Collector -External users

[Collista Lewingdon]

We are exploring the move from team managed to company managed and I am playing around with some of the features that are available in company managed projects, one of them being the issue collector. My question is, can the issue collector be filled out by someone who is not a licensed Jira user? For example, my employer is a school district and we use Jira internally in our administrative office but we have a project that the manager would like for unlicensed users to be able to created issues within the project to report feedback and/or bugs. I know that Jira forms in work management are only able to be filled out by licensed users. 

[Trudy Claspill · Accepted solution]

Hello @Collista Lewingdon 

Refer to this page concerning Issue Collectors.

https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/

An issue collector is accessed outside of Jira, from another website, so the users would not be directly working in Jira to create the issues.

The user accessing the issue collector does not need to be a licensed user of Jira.

[Justin A]

Trudy,

As Community Leader, would you please comment on the aspect of whether Jira, in such a case where "outside users" are submitting the Issue Collector form, would need to be setup as allow-anonymous-access, IF the users are being "matched" from your LDAP.

I believe that unless new issues will have the Reporter field set to a default person/user -- e.g. NOT set "Attempt to match submitter email address" -- then IF Jira tries to match the submitter's email to LDAP and tries to set the Reporter to the submitting user, THEN if Jira is NOT set to allow anonymous access, the form will fail.

In our Data Center instance, we've just locked down Confluence and Jira in order to save on concurrent licenses (previously we allowed anonymous viewing). Now our Jira users, when they haven't used the system in X-number of days, have their license revoked. When one of these users submits the Issue Collector form (say from a remote site, or even from a Confluence page), they get a 401 error returned into msg-container (an DOM container in the form modal) "401 - Oops, something went wrong...", and no issue is created in Jira.

Prior to this lock-down we didn't have this problem. Revoke the user's license, and now the form fails, UNLESS the Reporter will always be a default licensed user.

[Trudy Claspill]

Hello @Justin A 

The original Question has been marked as Answer Accepted and concerned the Cloud environment.

It seems like you are asking about the functionality of issue collectors in relation to a Data Center instance, and also in relation to other settings beyond the scope of the original question.

Given that you are diverging from the original, answered question in multiple ways, I recommend that you start a brand new Question. A new question will also appear on the first page of the Questions forum, whereas this Original post from 6 months ago is far down on the list. The only people who have seen your new question appended to this old post are the original author, me (because I responded to the original post) and any other community member who opted to Watch the post. That is a very small audience for your new question.

[Justin A]

Hi @Trudy Claspill 

I apologize if I wasn't conforming to best practices. I asked because I thought it might help the OP. @Collista Lewingdon .

Their question "My question is, can the issue collector be filled out by someone who is not a licensed Jira user?", I felt was not answered completely, as "The user accessing the issue collector does not need to be a licensed user of Jira" doesn't address when Jira is run without anonymous access.

I guess my follow-up question expands enough on this topic to inform the OP of the conditional circumstances I witnessed.

[Trudy Claspill]

In Jira Cloud the Issue Collector can be used without Jira configured to allow Anonymous Access. In that case the Issue Reporter setting for the Issue Collector must explicitly name a user that is licenses and has permissions to Create Issues in the target project. That information is contained within the documentation for which I provided a link.

If the OP was concerned about retaining the identity of the person that submitted the issue through the collector, and was not able to discern the answer from the documentation, I assume they would've asked more questions rather than mark the Answer as Accepted.

My suggestion that you start a new Question was motivated by you calling me out, specifically, asking me to comment on your question. As I mentioned, other community members would not be alerted to your update on this post. To get your question seen by a larger audience and better leverage crowd-sourcing for answers, you should start a new Question post. You are absolutely free to contribute more information to older, answered post. But if you want answers to new questions related to a post then you are better off starting a new Question and providing a link to the older, related post.