We have an issue with multiple linked and child issues, and we want to prevent users from adding more child or linked issues.
Is there a way to achieve this goal using automation, for example?
Hello @Jairo Muñoz Bolaños
Automation rules cannot prevent an event from occurring. Rules can only react to an event that has already occurred, such as the creation of an issue link.
An Automation Rule could react to such an event by undoing the event.
Can you tell us more about the conditions under which you want this to occur? Would you want this applied when an issue is in a particular status, or based on some other piece of data in some field?
Thanks for the answer Trudy.
This is a business request that applies to a specific issue. It could potentially change the status in the future.
If possible, having an automation, for example, to remove the last linked or child issue added while keeping the others would be ideal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What type of project is the issue in? Get that information from the Type column of the View All Projects page under the Projects menu.
You mentioned both "child" issues and "linked" issues.
1. Are you trying to prevent addition of child issues from the same project, or from other projects, or both?
2. Are you trying to prevent addition of linked issues from the same project, or from other projects, or both? Does the link type matter?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The project type is "Company-managed software"
1. Both
2. Both
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you checked this page?
If that doesn't work,. this might:
Regards
Aaron
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jairo Muñoz Bolaños ,
As per my knowledge we can't restrict based on the number of attachments, but we can restrict based on status of the jira issue (using workflow properties).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue I have is that this goal would apply to only one specific issue. Is that possible with the workflow properties?
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.