Need to prevent items from being added to closed features should require epic to be re-opened if a task needs to be assigned to it or force user to create new epic
So I thought that you could achieve this by setting the jira.issue.editable false property on the Done status since supposedly adding issues to an epic is controlled by the edit permission. However, I just spent a few moments trying this but it did not work. A bit perplexed by this TBH. There may be a way to do this using properties but I don't have time to investigate further. If you wish to play w/ this you might reference this site - https://www.j-tricks.com/
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.
Hi Satheesh - Welcome to the Atlassian Community!
I am not aware of a way to prevent an issue from being updated based on the value of another field in Jira Cloud. You might be able to accomplish that using ScriptRunner Behaviours if you have the Server version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @John Funk
Is there a way to prevent tasks/sub-tasks from being linked to epics that are marked as done status without behaviours.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, because you are really just updating a field on the issue.
Maybe the best thing to do would be to do a release to remove Done Epics from the board so they are not easily found.
Then you could create an Automation For Jira rule to email you whenever new issues are added to a Done Epic. You wouldn't be able to prevent it, but you would be aware of when it happened so you can educate the person and/or remove the link.
Actually, now that I think about it, you might be able to create a rule that removes the link automatically and emails the user that they are not allowed to do that, along with the instructions on how to properly modify the Epic.
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.
Ah, I forgot that you can't monitor for when the Epic Link field is changed in Automation For Jira.
Let me try to track down some more information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.