You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Our maintenance team creates a maintenance story with weekly maintenance subtask tickets. Other projects link their tickets to the weekly subtask ticket for maintenance they want done as well. They lock the maintenance window the day prior to the maintenance session to discuss and evaluate all of the changes. Users keep sneaking in linked jira's after the maintenance freeze, that aren't discovered until the middle of the work, which often cause problems during maintenance.
To solve that problem, I added a Maintenance status with properties "jira.permission.link.denied" and Maintenance window transitions with the same property. This works in removing the ability to link from the maintenance ticket. Once the weekly ticket is moved to Maintenance the "More -> Link" option is no longer available. However, other projects can still link their tickets to the weekly maintenance ticket.
How can I completely restrict all projects from linking to a particular jira that is in Maintenance Status?
Hi @Alicia Pena
I don't think you can get around with permission, even if you play with Link Issue permission on the target project it will not prevent other project to create links to an issue from this project.
If you have Scriptrunner you could do a script listener that listen link created event and delete it after creation if the destination issue in in "Freeze".
If you have automation for JIRA you can do a global automation that for each created link it will check the destination issue (select branch rule > Destination issue) then if the destination issue freeze date is pass then do some actions.
Actions can be adding a comment such as
The issue {{issue.key}} has been added after the freeze {{triggerIssue}}
Or you can tag the issue using a label or another customfield then create another automation trigger on this field update in order to remove linked issues (in this case do not forgot to check the box to allow the rule to be trigger by another rule in the detail section of the rule).
Regards
Thank you for your suggestions. I think I'll try the script runner option to stop link creations on tickets in maintenance status. Appreciate your feedback.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used the automation rule to comment on the jira if someone links a jira after it's moved to maintenance mode. That helps to identify those added after the ticket had moved to maintenance. Guess that will have to do until I figure out how to block links completely. Thank you Florian!
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.