Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Work only on own issues

Hi All,


We are using one particular classic project, in which users can create issues and work on them, but only that. They can only see and access issues created by them. Not the ones created by others.

This is super helpful when using JIRA for HR tasks or anything confidential that is only for the eyes of the particular employee.

We have a next gen project where I would like to apply the same permissions, but I am having difficulties setting it up. 

There doesn't seem to be an option to let a user see/work on their own issues and no others. Or am I missing something?



2 answers

0 votes
John Funk Community Leader Aug 18, 2020

Hi Rob,

I don't believe that Next-gen has the ability to do Issue Level Security which is what you would need. You would have to convert the project over to Classic Software otherwise. 

Thanks for your input, John. Is there an easier way to convert rather than having to re-create the entire workflow?

John Funk Community Leader Aug 19, 2020

No, because they are literally separate workflows and you can't copy Next-gen workflows.  :-(

Hey! Would you mind sharing the way you did it in a Classic project? Interesting!

Hi Valentin,

First I made a copy of the project's permissions, so I could mess around with them.

I adjusted the permissions so that only the project administrator has access to everything. For the obvious permissions, such as "Browse Projects", "Create Issues", "Transition Issues", etc. I set it up so the project admin, "Reporter" and "Current Assignee" have access. This way people were able to assign the ticket to somebody else and then only that other person being able to view it.

Not sure I did a great job of explaining, so here's a screenshot:

Screenshot 2021-02-01 at 22.23.04.png

Hi Rob. Thanks for the explanation.

Does this setup allow any Jira user to create an issue in it, even without access to "browse project"?

Hi Valentin,

Yes. You are circumventing that problem by having "Reporter" and "Assignee" listed for the "Browse Project" permission. It seems that it lets you access the project as you're a reporter, but not browse other issues, unless you're the reporter of said issue.

Like Valentin R_ likes this

Nice, will try it. Thank you!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,121 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you