How to allow any user to submit a ticket/request against your application

My team currently has a project in JIRA. We'd like for any user outside of our team to submit a ticket (bug, request, etc) against our application, but we don't want these external users to see everything else within our project.

Is there some way to "carve out a piece" of our project that only these users have access to? Or, perhaps, some other way to achieve this capability within our current project?

Or, do we have to create a whole separate project in order to do this?

3 answers

1 accepted

1 vote
Accepted answer

Hi Wendi,

You have options.

1. Use the JIRA Issue Collector for a web front end that will just collect values supplied and create issues (one way delivery).

2. Use email with no JIRA account holders at all, with JEMH to provide round trip notifications and some extras.

3. Use a combination of the Project Permissions and Issue Security configuration referred above, and either a bundled mail handler or JEMH. Users with JIRA accounts, without the right to login interactively can interact with JIRA through email, they can create issues, get updates, and JIRA security still applies, so the issue security scheme references above can still apply.

Thank you. This provides a nice, concise description of the options. Unfortunately, I will not be able to try them until my co-worker, who has admin privilege, returns to work and either gives me admin or can try it out himself.

Hi sugarman, In current project we can manage in permission schema to view or any particular operation in the project. If you want separate project that is also fine we can manage in the sameway. Regards, Patina

I found an answer to another question that gives a specific reference to the documentation for managing permissions,

Since my customer only has JIRA 5.0.2, I found the following documentation reference for this older version,

Feel free to answer/upvote if it helps you




You need to use issue security scheme to fulfil your needs.

Create a security scheme with levels - Visible to All and Internal Only.

Aply this scheme to your project and make all existing issues internal only.

Make sure everyone in your company has access to Visible to All and only your team has access to Internal only.

Now when another team member tries to raise an issue in your project, he will only get the option - Visible to All to select from. He wont see the option Internal Only.

Hope this helps.


Thank you. This sounds like the way to go. I have one follow-on question, though.

Would the 'visible to all' security level require the user to have a JIRA account? There are too many people in my company to issue everyone an account.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,213 views 5 10
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you