Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Preventing users from linking issues on a specific status

Lately, I have come across a few questions about using workflow properties to restrict actions when issues are on a particular status. Therefore, inspired by this jirakb, I thought it'd be helpful to write a short article to explore another possible configuration - to prevent users from linking issues on a Done status.

The examples and references you will find in this article are primarily related to Jira Cloud company-managed projects. Still, you can apply these configurations to Server/Data Center installations. However, If you're looking for workflow customizations on team-managed projects, check out the Work in Jira Software Cloud team-managed projects documentation.

 

Workflow properties

Basically, workflow properties offer a way to implement restrictions on certain workflow steps or transitions. You can learn more about how to use and configure workflow properties in the following documents:

 

Solution

1 - Edit the workflow step property of the status you want to restrict the ability to link issues.

2 - Select Properties

img2.png

3 - Add a New Property with the following parameters

  • Property Key: jira.permission.link.group
  • Property Value: <some-group>

For the property value, you should choose a group to grant permission to link issues. Thus, whoever is not a member of the group, won't be able to link issues.

It's important to mention that you can also use different parameters other than groups, such as project role. You also have the ability to configure the same property more than once by adding a suffix with incremental numbers. For example: jira.permission.link.group.1, jira.permission.link.group.2, etc. You can find more details about the available options at Permissions based on Workflow Status.

img3.png

4 - Go back to the workflow draft and click on Publish Draft. This is easy to forget, but without publishing it, the change won't take effect.

 

Results

Some of the behaviours you can expect after adding the property:

  • For users who are not in the jira-administrators group, the link issues button won't be available on the screen for the Done status issues; therefore, users won't have the ability to link issues.
  • When users create new linked issues, the "Linked issues" section won't display the Done status issues; e.g., if SAMPLE-1 is in the Done status, it won't be an available issue to establish the link.

img3.png

Before you go, make sure users have the link issues project permission to link an issue. Last, I know there is much more to share about this topic. So, feel free to chime in!

 

0 comments

Comment

Log in or Sign up to comment
TAGS

Community Events

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

Events near you