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.
Since you tagged this as cloud, this is my best suggestion:
At this point that one user you created and left out of that Group should not see any Projects.
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.
Thanks Tõnis, that worked perfectly!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.