Trudy P Claspill Community Champion

@Hareesh Welcome to the Atlassian community. Are you working with a Team Managed project or a Company Managed project? That information will display at the bottom of the navigation panel on the left when you are viewing the project. Alex's solution applies to Company Managed projects. If you are working with a Team Managed…

Olá @Lucia Maria Tavares , Você já tentou usar o Auxiliar de Permissões para diagnosticar esse problema? https://support.atlassian.com/jira-cloud-administration/docs/use-the-jira-admin-helper/ Se você não conseguir determinar a causa disso, compartilhe a saída conosco. --- Hello, Have you tried using the Permissions Helper…

Yes, you can do that through Issue Security Schemes/Level. Take a look at this documentation https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

After creating the parent task can you add a Log action to print the issue key to the Audit Log?

If you can run your rule on a Schedule, the Schedule trigger JQL will allow you to retrieve up to 1000 issues.

My {{issue.key}} was just an example of a smart value, not necessarily the smart value that should be used in this rule. I was trying to point out that the action is not limited to just the two options listed, and a smart value could be used to specify a different issue (if the rule is constructed such that a smart value…

Hello @Micah Kirkpatrick Welcome to the Atlassian community. I have added a tag to your post to alert the Atlassian Team to look into your issue.

Hello @Namrata Alinkeel Welcome to the Atlassian community. Are you working with a Team Managed project or a Company Managed project? That information will display at the bottom of the navigation pane on the left. For a Team Managed project to get a newly created issue to display on the board automatically you need to not…

Hello oterof@sancristobal.com.ar Welcome to the Atlassian community. You can't change the limit imposed on the Lookup Issues action. We need more information to provide useful alternatives. Approximately how many Epics do you expect to retrieve? Can you break that into to smaller groups, such as retrieving the Epics per…

Hello @Breanna Williams Can you share with us the details of the Audit Log? The status of "No actions performed" indicates the rule was triggered but that some condition in it was not met. The Audit Log will show those details. I suspect the problem is that you selected Parent for the For Related Issues branch. Notice that…

Please let us know what you learn from Atlassian Support, if you opened a support case.

Please let us know what you learn from Atlassian Support.

Several other users have reported the same problem in the posts linked before. Each has been encouraged to contact Atlassian Support directly. I recommend the same to you, and if you could report back to us here what you learn that would be wonderful. https://support.atlassian.com/contact/#/ I have not yet found anything…

Yes, that is the same way I'm reading it. We are missing information about how the rule is getting the value of the issue to which the trigger issue will be linked. It is possible that it is somehow retrieving that issue as part of the rule, in which case a smart value referencing that issue could be used.

Glad to help. If your problem has been resolved please consider mrrking the Answer as Accepted to help other users find posts with validated answers.

Hello Alicia, It is the Re-fetch issue data action that is causing that error. Try removing that. I thought it would be needed after a Create Issue action, but I guess it is not.

Hello @Rafael Welcome to the Atlassian community. This message is a normal and expected warning that you will receive when you add an item to an Active sprint. The scope of the sprint should be set before the sprint is started. Before starting the sprint you add the items to sprint that you expect to be able to complete…

Hello @Jose Miguel Hurtado Escobar Welcome to the Atlassian community. By default the roadmap will show the tasks with dates matching the Sprint dates. You can change the Roadmap configuration to use start and end dates from the issues themselves instead.

Hello @Kathryn Jenner You can enter a smart value in that field by clicking in the space that says Trigger issue and starting to type in the smart value. After completing the smart value entry you click on the Smart value '{{... text so that it will be entered into the field.

Great! If your problem has been solved please consider marking the Answer as Accepted to help other users find posts with validated solutions.

Hello @Alicia Simon The unexpected results have to do with your trigger. In your Scheduled trigger you have included a JQL. When you include a JQL in your Scheduled trigger you are telling the Automation that those are the issues you want to operate against. The steps in the automation will be executed for each issue…

It appears that Team is a single-select field, so I don't think it is possible to use that field to add multiple teams to a single Epic/issue.

Hello @Tomasz Swiniarski Welcome to the Atlassian community. You have to create a second rule that uses the Scheduled trigger .

Hello @Jamie Salter Welcome to the Atlassian community. You can use the Advanced Branching feature to loop over each value in the Vehicles Affected field to create a subtask for each one. Ignore the trigger in my example. That addresses the values that are specific vehicles, but doesn't address the need for multiple…

Hello @[deleted] You cannot refine the trigger itself for Issue Commented so that the rule is triggered for only comments that contain certain text. The rule itself will be triggered for every comment added. The best you can do is then add steps to limit the scope of the remaining activities. The rule is triggered by a…

Hello @Berzicai Lívia When you access the Automation screen you can find a Library of pre-built automation rule templates. Included in that library is a pre-built rule for what you want to do. Take a look at that and then let us know if you still have questions.

Hello @Jennifer Moreau Welcome to the Atlassian community. Is the documentation provided by the vendor not adequate? Have you considered contacting the vendor to get that support? There is a Support link on the same page I linked for the documentation.

Hello @Danilo Simic Take a look at the Answer from @Kian Stack Mumo Systems on this post. After the Lookup you need to add a branch to loop over the unique Procurement Initiator values (where the answer shows cars). Within the branch you do another Lookup for issues for each Procurement Initiator, and send an email with…

Hello @Mona Aghamirsalim After the trigger you have a step that is trying to check if issues match a condition. But at that point in the rule execution you have not specified the issues to operate against. The "If: all match" is not selecting the issues to operate against. It is determining if the issues previously…

Hello @Jared McNeil You should be able to do that with an Automation Rule. You could trigger the rule upon issue creation or on change to the Labels field. Then use Condition/ If-Else steps to evaluate the Labels field and set the Security Level. Note that the Actor of the rule would have to be a member of each Security…