Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you remove a closed JIRA epic for the list of Epic links?

Paul White
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 6, 2018

I read the similar questions and work around from 2 years ago but no solution has been proposed.  This is still very annoying to my team as we work through several closed Epics.  The list will continue to grow as we go froward and will become even more annoying.  Once the Epic is closed (and all related stories closed), how do we not see that Epic link when creating a new story?

We have reasons for keeping all closed stories and epics avail and the copy it off to a backup workaround is not acceptable to our team.  Thank you very much.

2 answers

1 accepted

1 vote
Answer accepted
TõnisO
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 8, 2016

Since you tagged this as cloud, this is my best suggestion:

  • Create a Group (https://{host}.atlassian.net/admin/groups), call it whatever you want (e.g. general-access) and put everyone in it except that one person.
  • Go to Permission Schemes (https://{host}.atlassian.net/secure/admin/ViewPermissionSchemes.jspa), edit the Browse Projects permission under Default Permission Scheme and instead of Any logged in user, enter the Group you created.

At this point that one user you created and left out of that Group should not see any Projects.

  • Create a new Permission Scheme where the Browse Projects permission is Any logged in user like it was for the default Scheme before.
  • Go to the One Project (https://{host}.net/plugins/servlet/project-config/{key}/permissions) and apply the new Permission Scheme to it.

End result: users in general-access will see all Projects (also the ones created after this change because you edited the default Scheme), the one User you left out of that Group will just see the Project (or Projects) that you have applied the new Scheme to.

Caveat: every new User you add to your instance that shouldn't be restricted to that one Project will need to be manually added to Group general-access.

ThomasRedstone
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 15, 2016

Thanks Tõnis, that worked perfectly!

0 votes
Avril Bower
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 9, 2016

Hi @Thomas Redstone, 

Also take a look at the accepted answer on this similar question: https://answers.atlassian.com/questions/39569399  

This is a solution I have used in the past to restrict vendors to just one project. 

Hope it helps, 

Avril 

 

Suggest an answer

Log in or Sign up to answer