Bill Sheboy Expert

Hi @Tony Conteiro For a question like this, please consider posting images of the complete automation rule and of the audit log details showing the execution. Those will provide context to help the community offer suggestions. Thanks! Until we see those...When you create the original ticket (or the clone) who are your…

Hi @Marcelo Ignacio Cid Abud This seems to be a duplicate of your other question. Please look there for responses: https://community.atlassian.com/t5/Jira-Software-questions/Count-Issue-Types/qaq-p/2337031 Thanks, and kind regards, Bill

Hi @Lana Decker Would you please post images of your complete rule and the audit log details showing the rule execution? Those may provide some context for what you are observing, and give the community ideas on what to suggest. Thanks! Until we see that... This could be a scoping problem, based on where you are performing…

Sure; glad to try to help... Let's say you want to know the average lead time (i.e., created to resolved dates) for items completed in the last 30 days. First you would create and test some JQL that returns the issues, such as this: project = myProjectName AND resolved >= -30d And, let's assume you want that average time…

Mentions in comments put in text like below, including the user's accountId value: [~accountid:theUsersAccountId] And so your rule could be triggered on issue commented, and then use the match() function to find if your specific user(s) accountId was used. You can find their accountId by trying a JQL search for them by…

Yup, and completely understand. I wish there was better/more configurable reporting built into Jira. The other free option I mentioned (an automation rule) could do this, such as run on a scheduled to send a single number. If you want to try that let me know and I can suggest a simple starting-point rule to try.

Hi @Ionut-Dan Nica -- Welcome to the Atlassian Community! When you search by enclosing the terms in quotation marks, it checks if all of the terms are present, in no particular order and with no exceptions for other words present. When you want an exact match, please enclose the entire expression in escaped quotation…

Hi @Karissa Do you mean... * for a single, specific user (e.g., you) who is mentioned in a comment, send a specific direct mention to them in Slack, or... * for any single user mentioned, send a direct mention to them I suspect #1 can be done by using a rule condition to look for the specific user's accountId in a mention,…

Perhaps also try these expressions to check the date without text formatting as jiraDate: {{issues.sprint.last.endDate.max}} to check one sprint value per issue, or {{issues.sprint.endDate.max}} to check all possible sprints for each issue (in case issues were in multiple sprints.

Hi @Trudy P Claspill -- I did have it on the view when I tried it in the rule with the direct field edit...it set the Due Date field to null after the edit, so I suspected there was something in the smart value, expression parsing.

I am glad to learn that helped, Tom.

Hi @Kathleen Buckwalter I just replicated your results, and suggest you submit a defect to Atlassian Support. It appears the Due Date cannot currently be set from the Issue Edit using the field selection. If you instead use the advanced edit with JSON, this work-around will work: { "fields": { "duedate":…

Hi @Alok Juneja First thing, I am using Jira Cloud and so do not have Server/Data Center to test this... I can think of two ways: * This should work, although more slowly: Rather than using Create Variable, use either an Entity Property on the issue or a custom field. When the value is set, use Re-fetch Issue to reload,…

Thanks, @Kevin Bui I am looking forward to trying this one!

I am glad to learn that helped. I find this symptom/defect curious as my understanding was that branches on one-and-only-one thing (e.g., branch to current issue) get converted to in-line code, as if the branch did not exist. Compare that to branches which could be on more than one thing (e.g., linked issues, JQL, etc.)…

I do not believe you need the For Current Issue branch as it is just nesting down from the trigger issue. Instead you can just reference {{issue}} or {{triggerIssue}} as needed. Please try removing that branch to see if the {{createdIssue}} smart value becomes more visible to the branch below it.

Hi @Rai Warbasse I believe you are seeing this defect/symptom where the {{createdIssue}} smart value is not visible to the scope outside of an if/else or branch in which the issue was created: https://jira.atlassian.com/browse/AUTO-154 Without seeing your entire automation rule, my suggestion would be to consider how you…

Hi @louis.haefliger -- Welcome to the Atlassian Community! First thing, I am not using assets...and so my suggestion is based on what I know about automation rules. It appears you are trying to find the differences in the field between before/after to set your Summary and Description fields. Have you tried using the added…

Hi @Brandon Criger Would you please post images of your complete rule and the audit log details showing the rule execution? Those may provide context for what you are observing and help the community to offer suggestions. Thanks! Until we see that information...how are you adding the components, by name, id, etc.? Using…

Hi @Russell Brown What problem are you trying to solve by doing this? Knowing that may help the community to point you to useful references. And consider also posting this same question in the developer community area for other ideas: https://community.developer.atlassian.com/ Kind regards, Bill

Hi @Abhishek -- Welcome to the Atlassian Community! Is this a project scope or a global/multi-project scope rule? * If this is project scope rule, you could add an "indicator" to the trigger issue, such as a custom field or comment, specifying the cloned-to teams. And then use rule conditions to prevent adding duplicates…

Thanks for that information. Based on what you described, perhaps try: * swim lanes by epics, * add quick filters by tiger team, and see how that flows for the standup. * When you also need the assignee-specific view, that is already built into boards by selecting the avatars. With those configurations, anyone who can see…

Hi @Kevin Bui Thanks for the information on the new feature. I do not see this in my instances yet and so I wonder: what is the type of these input fields? Are they always text or are they type-configurable like custom fields? Kind regards, Bill

Hi @sai chinamuthevi I do not believe that is possible with out-of-the-box features. If you only had one grouping category (i.e., Assignee OR Label), you could create such a report using an automation rule. With two groups you could either export to a spreadsheet and use a pivot table report or investigate the Atlassian…

Hi @Neil Wills Yes, and...to Trudy's answer: Would you please describe the flow of your teams' use of the boards and the "standup"? And, how do epics fit into this for the different tiger teams? I ask because I wonder if quick filters (by tiger team) would be sufficient for the standup part you describe. Kind regards, Bill

Thanks for that information. Next thing to try: smart values are name, spacing, and case-sensitive. And, the one for Due Date is normally this {{issue.duedate}} so perhaps try this for updating the next issue: {{createdIssue.duedate}} I also recommend writing {{createdIssue.duedate}} to the audit log to confirm it works as…

Hi @Dario Pereyra and @StonikByte I just checked and that gadget is working for our site, and I do not see issues on the vendor's status page. You may want to ping their support team to ask for help: https://marketplace.atlassian.com/apps/1216564/great-gadgets-for-jira-cloud?hosting=cloud&tab=support And the error seems to…

Hi @Eric Younkin When you have an Epic with child Tasks, they normally do not use linking that way. Instead the Tasks all just have the same Parent (or Epic Link) value to point to the Epic. Why are you using links to connect them? Next thing: for a question like this, please post images of your complete automation rule…

Hi @Michael Byers -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud, not Server/Data Center, and so my answer is based on what I know about automation rules. The Server/Data Center version has the ability to bulk-handle issues for a branch or scheduled trigger with…

Hi @Lydia M Please try using the displayName attribute for user fields, such as with {{issue.reporter.displayName}} : https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/ Kind regards, Bill