Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Attempt to follow an example where you restrict closing of issues to only a QA user

(For context: Jira Cloud Standard. Attempt to follow an example where you restrict closing of issues to only a QA user.)

I tried following the steps here to setup a project role called QA:

What I found was that the default out of the box project has no resolution field. The default workflow has no close. I added 'close' to the workflow but, that only updates the 'status' field, not the resolution field. So, I went a step further and added the 'resolution' field to all my screens so I'd have access to it. But, now I cannot create an issue without setting a resolution and the only default resolutions do-not-include 'Unresolved' which is what the ticket would be when it is opened. 

Possible solutions:

1: I could add 'Unresolved' to the 'Resolution' field, but then the issue creator would have to have access to update the field and since I am attempting to restrict that to only QA then that seems to not solve the problem. I would have to get QA to create and close all the issues. 

2: There must be a way (post function?) to add the field part way through the ticket? No that is madness. Why would you do that?

3. Update the default template and allow the field to be null? This might work I suppose. 

Is Atlasssian dropping 'Resolution' for some reason? 

1 answer

1 accepted

0 votes
Answer accepted

So I was using the docs for Server but using Cloud. I can find no equivalent document for cloud and according to adaptivist video bellow the post function are async in the cloud so they can't prevent transitions. It might not be possible to do it, which is probably why there is no cloud version of this document. Or there is some suggestion of injecting javascript, but since I am just learning I don't think I need to solve this right now. I can just follow the cloud docs.


Also it is not good to make a status of 'Unrelsolved' accoding to the docs. 


Don't create a Resolution named "Unresolved"/"None"

Any issue that has the Resolution field set is treated by Jira applications as "resolved". The Issue Navigator displays Unresolved when no resolution is set for an issue. So adding a resolution named Unresolved/None and setting it in an issue will mean that the issue is seen as resolved. This will lead to confusion and is not recommended.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

278 views 16 17
Read article

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