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

No close issue button

I have created the group "projectmanagers" but somehow users of this group don't see the "close issue" button and are therefore unable to close issues.
I am using a copy of the default Jira workflow but it's unclear to me what I should change to make this button appear in their interface. (I have adjusted the permission scheme: the group Projectmanagers have the right to close an issue) Can you please advise?

3 answers

Issues like this are precisely why JIRA cannot be taken seriously.  The complexity of its configuration might be acceptable and even valuable for a massive project with a full-time JIRA administrator.  But for everyone else, it's massive overkill.  And it's ridiculous that the out-of-the-box configuration is completely unusable.

Add this to the bizarre and inconsistent UI, and it's just too much.  Goodbye, Jira... and good riddance.

You can't have it both ways. If you want the flexibility JIRA offers, you have to be able to set it up, and that means complex administration. As for the out-of-the box config being unusable, that suggests you've not even tried. It works, and it's simple.

Jira seems to show categories as Status but when I go to add a new Status it has all these Status names - like Closed - which I want.  How do I close

You don't say what "category" you mean - there are two different uses of that word in Jira-speak.  But neither of them matter to "how do I close"

To close an issue, use a transition that takes it into a closed status.  You'll need to check your workflow to see what you can and can't do from the current status.

0 votes

Look at the transition in the workflow - check what the "conditions" say.

I suspect it's more complex than just "users must have close-issue permission" - it might have "and users must have resolve-issue permission" tacked on to it as well

@Nic BroughThank you for your answer. I agree and think the problem is based somewhere in the 'workflow' configuration. However I have not been able to find a solution yet. As a temporary solution I have added the users to the developers group, where they can close issues but that of course won't do for the long term solution.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

342 views 1 3
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