We have Requirement to Hide an an Issue Linked to the Other Issue.
Eg:I have Issue with Key EG-1 Linked to EG-2, can I hide EG-1 to make it invisible which is linked to EG-2.
Doesn't make a lot of sense to link an issue, and then hide the link. Might as well not bother linking it.
If the user can't see the issue at the other end of the link, it does make sense to hide the link (in fact, you need to, to avoid leaking data), and JIRA already does that.
Under different circumstances it would make sense.
Lets say you're using issue matrix in order to see not only the current status and instead also specific values in related issues without the demand to check every related issue manually (which quickly can become a bunch of issues). Out of the box - as far as I know - that is impossible.
However, given that we're now having a couple of lists of related issues. The default one and the far more saying issue matrix section. I think the default one is obsolete then, isn't it? At this point, however, our customer (who is not yet really familiar with Jira) would be confused.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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