Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,553,229
Community Members
 
Community Events
184
Community Groups

How to restrict Linked Issues to the Project they're created in

We have multiple active Projects. When creating an Issue, the Linked Issues field will populate suggestions from all of our Projects. We'd like to restrict this to only suggest Issues from the current Project, just as the Sprints field has an 'Only Show Sprints in this Project' toggle.

2 answers

1 accepted

0 votes
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 07, 2023

Hi @Jordan Kleeman 

You can't restrict the users (in cloud), to choose only from a specific project. However, what you could do, if you have an app like JMWE, JWT, Scriptrunner, JSU etc, then:

  • If the users are linking issues via a transition screen, to allow that transition only if the linked issues belong to the specific project.
  • If the linked issues is available on the edit screen, to possibly add an event when the linked issues are changed, and to validate that the linked issues belong to the specific project. If they are not, then erase the linked issue. This is not the best approach, since the user might be a bit confused about why his linked was erased, but it is a viable solution.

There is an open suggestion here https://jira.atlassian.com/browse/JRACLOUD-9634 which you can vote and watch. There was also the newer suggestion here https://jira.atlassian.com/browse/JRACLOUD-36494, but the older one (9634) is the one to follow.

Hi @Jordan Kleeman and thank you again @Alex Koxaras _Relational_ for mentioning us!

I am part of the Support Team of Decadis and I will gladly help you with the alternative solution that @Alex Koxaras _Relational_ proposed using Jira Workflow Toolbox for Jira Cloud.

It would be possible to validate during a transition if all of the linked issues of the transitioned issue are in the project of the transitioned issue with a Jira expression validator. It would only be necessary to enter the following expression to set it up:

issue.links.every(l => l.linkedIssue.project.key == issue?.project?.key)

Some more use cases for our Jira expression validator can be found in our documentation, namely in the page Jira expression condition/validator (use cases).

Please, let us know if you need further assistance in this thread or via our Support Service Desk.

Best regards,

Vicente

0 votes
Matt Doar__ LinkedIn
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 07, 2023

If you use subtasks they all have to be in the same project as the parent issue. But they are only 1:N not N:M

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events