Bill Sheboy Expert

Hi @Ena Garner -- Welcome to the Atlassian Community! What version of Jira are you using? If I assume you are using Jira Cloud, you could: * Navigate from the top bar to Filters > Advanced Issue Search * Create your query, and select search * Confirm you got what you wanted * At the top-right of the page view, select…

And...those fancy quotation marks when copy/pasting solutions into Jira JQL ;^)

Yes, and...to also check for issues with no parent epic: project = APT AND key != APT-16 AND ("Epic Link" != APT-16 OR "Epic Link" IS EMPTY)

Hi @Michael Puglin Cloning an issue and its related issues in one step is in the automation backlog as a suggestion: https://codebarrel.atlassian.net/browse/AUT-998 As a work-around you could do this in pieces to clone the issues and link them, or instead have the automation rule create the template issues directly. Best…

Hi @Paul Treadwell -- Welcome to the Atlassian Community! Yes, and... to Jack's answer: One work-around to keep the name visible in your quick filters is to use this syntax: assignee IN ("Paul Treadwell") Best regards, Bill

Hi @Thiago Cunha I believe you have listed many of the methods teams use; the details are in how to use Jira to help manage and visualize those. "Taking it to the team" can help figure out what they believe could be tried and improved. At this time, one limitation is whether you are using company-managed projects or…

Thanks for clarifying. For the new issue view, when I open an epic in the side-bar (right side of page) I see the color as a selectable/editable item next to the summary name, and not as a field. Would that work for you?

Hi @Laurie Anci Are you trying to change the epic color for its display with issues? If so: * for team-managed projects, when viewing the epic you may select the color next to the summary to edit to a new color * for company-managed projects, you may change the epic color the same as for team-managed, or change the color…

Hi @Stef Green You are describing two different issues, so let's look at them separately: a timing problem and field-set on issue creation. Timing problem * Your rule design will lead to multiple executions when there are multiple tasks in the epic. That seems to be what you intend. This will occur no matter how fast you…

Hi @lebigot You note that the condition "doesn't work". What exactly is happening? And, for a case where you expect the rule to work, please post an image of the audit log details. Thanks! Best regards, Bill

Hi @Manoj Khaire You appear to be on Jira Cloud version, correct? If so...with the built-in Automation for Jira and a custom field, you could compute and report on Age of WIP. Here is the how-to: https://community.atlassian.com/t5/Automation-discussions/What-is-your-most-useful-automation-Here-is-mine/m-p/1561072#M34 Best…

Hi @Sitt Sen Chok -- Welcome to the Atlassian Community! Adding to what Jack suggests, I recommend disabling the delete permission except for the site admin users. Instead consider adding an "abandoned" custom field, and people can mark issues as such. To hide these issues from backlogs, boards, and reporting, change the…

Hi @Ibrahim Ghalghay When you want to run a rule on a set of issues, one by one, and do not yet have a triggering event (e.g. sprint completed), you can work-around this by: * change your rule trigger to "issue commented" and check for a specific comment value * bulk change the issues from advanced search to add the…

Hi, and sorry I was not more clear on the approach. Please take a look at this documentation for Lookup Issues: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/#Smartvaluesgeneral---lookupIssues-- This action uses JQL to gather a set of issues. You wanted to find issues for an epic where the…

Hi @Jody McMillan -- Welcome to the Atlassian Community! Please take a look at this post, and scroll down to the comments from the Atlassian folks as they list some open defects and possible causes of this symptom:…

Hi @Panos Rigopoulos What type of project are you using: company-managed or team-managed? And are you using a Kanban or Scrum board? I wonder if your filter is hiding issues associated to a released version. If so, you may need to adjust your filter to account for this edge case of incomplete issues in a released version.…

Hi @Sonda LiderBci -- Welcome to the Atlassian Community! If your external tools have a REST API and you are able to set up a webhook to listen for, you could use Automation for Jira (A4J) which is included in Jira Cloud. Please look at these sources for information: *…

You could try calling this REST API method with your search, and expand the changelog: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/search-search

Hi @Mark Anderson How about this: project = myProject AND issueType = story AND ( issueLinkType != "is tested by" OR issueLinkType IS EMPTY ) https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Advancedsearchingfieldsreference-issuelinktypeIssuelinktype Best regards, Bill

Hi @appsmobiliojivisata No, other users will not see the unsaved changes, and this is a behavior/problem to watch for in the new issue view... We recently had one user edit a field, click elsewhere on the page, and that resulted in unsaved changes. Those changes stuck around for over a month in the cloud...eventually when…

Please try removing the math operators and just use the smart value, divided by 2. That worked for me.

Hi @Steve Steve Adding to Sarah's ideas for visualizing cycle time, if you need the data outside of Jira, you could: * use a marketplace addon for JQL which supports calculated fields * use a marketplace addon specifically for workflow/process measurement * use custom fields and Automation for Jira (A4J) to capture changes…

Hi @Kasper Sørensen and @Trudy P Claspill How about this: * use LookupIssues with JQL where the epic link is the target and team is "Team X" * When {{lookupIssues.size|0}} is greater than 0 set the epic's team to match * Otherwise, clear the epic's team Best regards, Bill

Hi @Damla Naz Yilmaz No; I do not believe there is a generic iterator/looping structure in automation rules yet. Here is one suggestion to add that feature: https://jira.atlassian.com/browse/JRACLOUD-76906 If you know the list of custom fields, you could include each one as an edit in the rule, and then repeatedly parse…

Hi @Wiliam Joaquim Yes, and...to what Jack describes, the card limit feature (work in progress, or WIP) provides a visual indicator to a team that adding a card exceeds a policy that the team has defined. That may be acceptable, such as an expedited item, or it may not; this depends upon the team's policy. I suggest there…

Hi @Ondřej Medek Adding to what John suggests, only a site admin for a paid account can submit a defect to Atlassian. Please ask your site admin to submit what you perceive to be the issue. Best regards, Bill

Hi @Vandyck Lai Kai Yong Have you tried using the change log to access this value? For example, this would return the ID of the previous assignee, assuming you have the same trigger of field change on assignee: {{changelog.assignee.from}} Best regards, Bill

Thanks for that information, Robert. I can see that each one of these report ideas could lead to a conversation, uncovering more details. For example and looking at (1): What do you mean, "categorized by age"? What is age: time since created, since work started, etc.? What is "long pending" and how long is "overdue"? I…

Awesome! I am glad that worked for you. Have a good one!

Hi @Hauke Bruno Wollentin -- Welcome to the Atlassian Community! Thanks for that reminder about the spacing, and... your link seems to have some extra chars making it fail. Here's one that works: https://community.atlassian.com/t5/Automation-articles/New-automation-smart-values-in-Jira-Cloud/ba-p/1402775 Best regards, Bill