Trudy P Claspill Community Champion

You can also iterate through the results set of a Lookup Issues action to make changes to each issue in it. There is an example of that in the answer on this post.

Hello @Gena Welk Is there a reason that you are not using a Saved Filter with a Subscription to deliver that information, rather than an Automation Rule? https://support.atlassian.com/jira-software-cloud/docs/work-with-search-results/#Workingwithsearchresults-subscribeSubscribetosearchresults If you decide you want to…

Hello @Mallory Sauer These are changes that Atlassian has been working on to align Company Managed and Team Managed projects to handle Epics in the same way. This particular change was called out in their weekly updates blog. https://confluence.atlassian.com/cloud/blog/2023/04/atlassian-cloud-changes-mar-27-to-apr-3-2023…

In that case you would need to be able to pick Issues in that field. Currently Team Managed projects don't support a custom field that allows you to select an issue like the Linked Issues feature does.

You're welcome! If your question has been answered, please consider marking the Answer as Accepted to help other users find posts with validated solutions.

When I try by date created (\"20/mar/23\")") it returns nothing though I know 3 tasks with 69 subtasks were created on that day That is because that is not valid syntax. Also note that the Created value is a date and time. You need to consider that in your JQL. If you want issues created on a specific date then you need:…

This page talks about the smart values available under the {{issue}} object. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ There is not a "link" smart value. You could manually construct it in your email content thus https://<yourURL>.atlassian.net/browse/{{issue.key}} Substitute the…

If you added it as a custom field then you define how it works. You start by defining the type of custom field you are adding. It appears that you added it as a Drop Down field. You can learn more about the types of custom fields that can be added to a Team Managed project and what each type does here:…

Hello @Albert Hristov For a Work Management project you cannot customize that navigation bar that you have highlighted. Work Management projects cannot combine information from multiple projects into one display. Each Work Management project interface displays the data for only one Work Management project. What views are…

Hello @Natalie Mickan Welcome to the Atlassian community. Can you provide a screen image of what you are seeing?

Hello @Susan Gardella Welcome to the Atlassian community. You could change the underlying Rich Filter that is used by the gadget so that it selects only those issues. You could change the Working Query defined in that instance of the gadget to constrain the results. If you share with us the details of your Rich Filter we…

I believe your "Dependency" field is a custom field specific to your environment. I don't know what it is for or how it works. Are you working with a Company Managed project or a Team Managed project? If you are working with a Company Managed project you can confirm it is a custom field by going to the Custom Fields screen…

Hello @Ekow Essel Welcome to the Atlassian community. Are you importing the issue into a Company Managed project or a Team Managed project? Currently it is not possible to set the parent Epic for a child issue if you are importing to a Team Managed project. That is noted in this issue:…

Hello @ADENUGES2282 Welcome to the Atlassian community! How is the query not giving you the results that you want? What is it including that you think it should not? What is it excluding that you think it should include? "issueFunction in subtasksOf()" will give you the subtasks of the issues that match the criteria in the…

Hello @Ezraa Douglass Welcome to the Atlassian community! Yes, you can. Try this: (issueType = Epic and status="In Progress") or issueType=Task

Hello @Venkata Sagar Ganesh Rao Mahendrakar Jira does not natively allow you to compare two date fields directly in a JQL statement. You might be able to do that with a third party app that extends JQL functionality. Are you open to acquiring such an app? How often do you need to get this report? Will the time period…

Hello @Fabrice Vailhen Welcome to the Atlassian community. To get the linked issues of a particular type the native JQL syntax would be: issue in linkedIssues(<source issue>, ) Example: issue in linkedIssues("AAA-12","is blocked by") This could return multiple issues that are linked to AAA-12 with the "is blocked by" link…

In a Team Managed Software project the Resolution/Resolved fields should be getting set automatically when an issue is transitioned to a status in the Done Status Category. Those are the statuses that show up as Green in the workflow. When you look at the board for your project you should see a green checkmark at the top…

If you are trying to insert into the email the key (i.e. ABC-123) of the issue that triggered the rule you would paste into the email Content field {{issue.key}}

Thank you for that screen image. What you are seeing as the Dependency field is a custom field that was added to your Jira system/project. That is not the field that is used to indicate a dependency between issues for the Roadmap function. For the Roadmap function, a dependency between issues is indicated in the Linked…

Hello @Andrea Ferraris Welcome to the Atlassian community. I recommend that you start by using the Log Action to print out your variables and your calculated values into the Audit Log to ensure you are getting the values that you expect. Can you show us the Audit Log for the rule execution?

Hello @Chad R Brown Are you working with a Team Managed or Company Managed project? That information will show at the bottom of the navigation panel on the left when you are viewing the project. Are you working with a Software, Service, or Work Management project? When viewing the project Software and Service projects will…

Hello @Laurie Cassity Welcome to the Atlassian community! assignee in (user1, user2) and status in (done, complete, "ready for release") That will get you the issues assigned to those two users that are currently in the "done" statuses. If you are setting the Resolution field during those transitions, which you should be,…

Do you have the correct syntax now? If not, please show us what you have so we can help you correct it.

If you have been able to successfully complete the automation rule and it is working as you desire, please consider marking the Answer as Accepted to help other users find posts with validated solutions.

If you choose to use an Automation Rule for this, you can use smart values to add information about the issue to the email content. https://support.atlassian.com/cloud-automation/docs/what-are-smart-values/

Can you show us a screen image that shows the link between the issues and what you see for the Dependency drop down?

Hello @Ivan Soldo Welcome to the Atlassian community! Since the original post has an Accepted Answer, please start a new Question thread to get help with your scenario. Only the people who have participated on the original thread or are watching it have seen your question added to it. In your new Question please also tell…

There currently is not a native JQL method for getting all the descendant issues through all levels of the hierarchy, down through the child issues under Epics, supplying only the issue key of an issue at a level above Epics. There is a change request about that here: https://jira.atlassian.com/browse/JSWCLOUD-19543 The…

This is the rule that you need. In the JQL where I have or issuetype="QC Sub-task" ...you need to include all the possible sub-task types that you want to ignore that could exist under the parent issue. or (issuetype in ("QC_SubTask", "BA_SubTask", "Sub-Bug")) The net effect of the condition is to check all the Sub-tasks…