Hi Atlassian Community,
We recently migrated from Jira Data Center to Jira Cloud. Some of our previous custom field–based relationship links have been migrated as Advanced Links (STAGIL Plugin)
We are now trying to define best-practice guidance for our teams on when to use Advanced Links versus Jira’s standard Linked Work Items / Issue Links.
Our key concern is that although we can build JQL queries using Advanced Links, we are unable to display Advanced Links as columns in Jira Search / Issue Navigator or in Structure. This limits our ability to use these relationships for reporting, review, sorting, and portfolio visibility.
Could you please advise:
We want to avoid inconsistent usage across teams and define a clear standard following our migration to Jira Cloud.
Thanks,
Noopur
Hey @Noopur Agarwal ,
Interesting question... Can you share which app exactly you are using? I've explored Marketplace a bit but couldn't find the app with that exact name. 👀
Anyway, I haven't used Advanced Links, and I'd like to hear how people are actually using them. From what I have researched, these are mainly used for complex data modeling or for specific plugin-driven visualizations. 🤔
Jira columns do support native fields, and even some Forge fields cannot be displayed there. So, I'd say that this behavior you're seeing is expected. As for Structure, I believe the same applies to that.
Have you reached the vendor (STAGIL) directly to see what they have to say about this and whether they have any recommendations?
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.