Trudy P Claspill Community Champion

Thank you for that additional information. Have you verified that the issue that triggered the rule has issues linked to it, using the View All Issues interface? Are the issues linked to it in the same project as it, or different projects? What is the Scope for the rule according to the Rule Details page? If the linked…

The good news is that all these boards refer to the same project. There is no need to "move" issues. And it is perfectly acceptable to have both Kanban and Scrum boards referencing the same project/issues. I am curious about the management of work being mostly kanban with a few sprints throughout the year. What is the…

Hello @Amith Reddy Welcome to the Atlassian community! Can you provide more information? Are you asking how such a rule could be constructed? What is the field type of the custom field? Does that custom field value exist in the parent or the child? What type of project are you using? Get that information from the View All…

The position suggest that it could be the built-in filter for the Epic issue type. Did you previously see "Epic" in that position? Are you able to create an "Epic" issue type in these projects? Or do you now see a "PLC" issue type instead?

That is correct. That limitation is documented here: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ One way to work around this would be to: 1. Update the sum stored in the initiative to 0 at the beginning of the rule. Then re-fetch the issue. 2. Use a Lookup Issues action that is more…

Hello @Ken Siskind Quick Filters can be created by the board administrators. You will need to ask your board administrators about that Quick Filter. I doubt that is something provided natively by Jira, but if you provide a screen image we can confirm that.

Hello @Benjamin Welcome to the Atlassian community. Here are a couple of the impacts of deleting boards. Dashboard gadgets and Automation Rules may refer to agile boards. If you delete the referenced board then the gadgets and rules will stop working. When you delete a board you will lose access to the Reports section that…

Hello @Rachel O_Loughlin Welcome to the Atlassian community! When you say the issues are duplicated do you mean there are two issues with different issue keys but the same content? Or do you mean one issues is shown on more than one board? Boards display issues based on a filter. An issue can be within the results of…

Hello @Francis Calderisi What is the Scope of the rule from the Rule Details page? The Lookup Issues action is able to retrieve issues only from the projects that are listed in the rule Scope. I notice that the issue that triggers the rule in in the RM project. In the image you provided from the Issues screen I see that…

Hello @Jan-Willem Aikens There is a difference between the functionality of agile boards for Company Managed projects vs. Team Managed projects when the Kanban board has the Backlog screen enabled. With Company Managed projects, display on a Kanban board vs. the Backlog is based on the Status value of the issue. With Team…

With Jira Admin access you should be able to create a copy of the Permission Scheme currently used by the project. Then modify that copy to restrict who has the Assignable User permission. Then set the project to use that new Permission Scheme, through Project Settings / Permissions.

Please provide images showing your current rule and details of each step, since you have modified it. You may want to try adding a Re-fetch Issue action to you rule, after the trigger. Sometimes the trigger happens before all data has been saved. The Re-fetch Issue action will re-query Jira to get the current data. You can…

Hello @Kelly Peck What information is available in the rule execution Audit Log? Does it show the rule executing the action multiple times? Does it show the rule being executed twice? How are you setting the To field for the Send Email action?

Hello @Adi Sashkis Welcome to the Atlassian community. When asking for help with an Automation Rule it will enable us to help you more effectively if you provide screen images of your entire rule and each step in the rule. Please also provide the details from the rule execution log. And please explain to us what you are…

Moving a card from one column on the board to another column on the board is based on the Transition Issue permission. That is the ability to transition the issue from one Status to another Status. You'll need to remove the groups/roles/etc. assigned to that permission. There is also the ability to move an issue up and…

Hello @Raymond Correa Welcome to the Atlassian community. Values that exist currently in the Labels field should be available for use in the Labels field of all issues in all projects in a Jira instance. If that is not your experience can you provide some screen images showing that the values exist currently in an issue,…

The user that can be assigned to issues in a Company Managed project are those that have the Assignable User permission for that project. Changes to the permission scheme can be made only by a Jira/Product Administrator. If you don't have that level of açcess you'll need to talk to some body that does. They can make a copy…

Dear Trudy, Is there a potential solution to my problem? Thanks! Did you review the article I linked in my last response? It provides a few options. https://confluence.atlassian.com/jirakb/how-to-restrict-issue-creation-for-a-particular-issue-type-based-on-roles-in-jira-server-960701303.html

Hello @Sarah Bizewski When asking for help with an automation rule it will help us help you more effectively if you provide screen images show your entire rule and the details of each step. It sounds like you need a rule to automatically copy comments from the new ticket into the the ticket that cased the creation of the…

Hello @Andre de Castro Whenever you ask for help with an Automation Rule, it will enable us to help you more effectively if you provide screen images showing the entire rule and the details of each step. We can't advise you on how to improve a rule when we don't know the components of the rule you're trying to improve.

Can we agree on the meaning of these two statements? * A blocks B. This is equivalent to saying "B is blocked by A". * A is blocked by B This is equivalent to saying "B blocks A". Statement 1 says that A must be completed before B can start. That is the definition of "blocks" Statement 2 says that B must be completed…

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.comments-- Try this instead: {{comments.last.body}}

Hello @Gleica What is the project type for the YMD project? Get that information from the View All Projects page under the Projects menu. What you have highlighted in the second image is a Story and its Sub-task. Subtasks will display nested under their parent issue. This is a special feature of Subtasks. The same feature…

Hello @Patrick Sullivan Welcome to the Atlassian community. The native linkedIssues() function will require you to enter just a single "source" issue (the issue to which the results issues are linked). https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#linkedissue You would have to have that function in…

My apologies! I made a mistake. Within the email content you do need the curly braces around the field names: {{key}},{{created}}, etc. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

Hello @lucie.bednarikova Welcome to the Atlassian community. The Edit action is about editing the issue, not about updating a created variable. There is no action available for updating an existing variable. The only action available is Create Variable, which replaces the value of the existing variable. Do I understand…

Hello @lori lins Welcome to the Atlassian community! Each row in the CSV represents an issue, so you would add the existing issue key as a new column in each row. To update the issues you also need to include the Summary field and Issue Type. Otherwise include only the columns for the fields you want to update. To execute…

Hello @Garth Bond Welcome to the Atlassian community! It is unclear to me what you mean by "at the task level" in the context of the company's Jira configuration. The default issue type hierarchy for Jira is: Epic (level 1) |-- standard issues (level 0) i.e. Story, Task, Bug |-- subtask issues (level -1) For Sprint…

Hello @Gleica Welcome to the Atlassian community! Can you provide screen images to show us what you are seeing, both for the Story + Epic, and for a Task/Bug/Other type that is not showing in the same way?

Hello @Francis Calderisi Welcome to the Atlassian community. Can you show us the results of the JQL query using the issue key shown in the log? I want to see the Issue Types for the issues in the results. The other information can be obscured.