Bill Sheboy Expert

Hi @Cristian -- Welcome to the Atlassian Community! To clarify a bit, are you describing that your rule is not triggering, that there is not response to the webrequest, or something else? Perhaps showing the audit log details for when this rule runs will help reveal something to explain the symptoms you are observing. Kind…

Hi @Jonathan Cunliffe My understanding is that mentions only email the user and do not add them as Watchers. It would be possible to write a rule, triggered on comments, which finds any mentioned users' accountId values and then adds them as Watchers. I recall several posts on doing that here in the community. Kind…

Awesome, and I am glad that helped! To see information on the specifics of the time-in-status, you could try Atlassian's interpretation of the Control Chart report for your board. There are some limitations on that chart, so if you want something better / different your options may be driven by what you want to build or…

Thanks for that information. Let's first try the simplest thing which could fix this symptom: * The issue created trigger can fire fast...so fast that the data is not available when the condition tests the issue type...and so the condition fails. * The work-around for that is to add a Re-fetch Issue action immediately…

Thanks for that information. I have not used that addon tool, and I recommend contacting the vendor directly to learn if what you ask is possible.

Well done! What would you expect to happen if another value is added, and target value is already in the selections? For example from your question, "Test".

Hi @Joshua Wyss Yes, and...to John's answers... For your second case, you are encountering the problem where changelog seems not to be working lately with smart values for multi-select and multi-value fields (user-picker, fixVersion, labels, etc.) Until that is fixed (added?) work-arounds are messy. One approach is to…

Hi @oliver.peacey Short answer: this is not currently possible with automation rules...but you can get close. Longer answer: I recall there are recent, open defects that the changelog access within automation rules is not working for fields using lists, such as for labels, fixVersion, etc. So you may not be able to exactly…

Hi @John Cross -- Welcome to the Atlassian Community! Yes, and...to Mikael's answer: Here is the link to the specific improvement item for sharing custom fields between team-managed projects; Atlassian says it is currently scheduled for availability in January 2023. You may watch/vote for it to see progress:…

Hi @Bertrand Samson -- Welcome to the Atlassian Community! I do not believe that is possible, and perhaps try emailing that vendor directly to see what they say: https://marketplace.atlassian.com/apps/1213231/issue-checklist-for-jira-pro?hosting=cloud&tab=support Kind regards, Bill

Hi @André de Oliveira Águila Favoto -- Welcome to the Atlassian Community! The statusCategoryChangedDate summarizes the movement through the workflow by statusCategory: to do, in progress, and done. If all you want is when issues reach "Done", have you tried to use Resolved instead? That field can be exported. Kind…

Hi @Jérôme RAVIER Some things to check for this symptom would be: * What is the type/source of your custom field? For example, is it a single-select field, with a drop-down...or perhaps a calculated field from an addon app? If it is calculated that might explain what you are seeing as some values do not evaluate inside of…

Hi @Gentrit Cerimi You note that you want to implement an automation rule to solve this need. What have you tried thus far to accomplish this? Please consider posting images of your current rule, details from the audit log, and describe what is not working. Kind regards, Bill

Hi @Nitzan Matalon I do not see a Sprint Capacity addon in the marketplace from Atlassian. Perhaps you could clarify which one you are using. And...if this is from a different vendor, please check their support page to learn how to do what you ask. Kind regards, Bill

Hi @Maggie Haefele -- Welcome to the Atlassian Community! What types of project are you using for the source/destination: company-managed projects (CMP), team-managed projects (TMP), or one of each? If either of the project types is TMP, this could explain what you are observing as custom fields in those projects are…

Hi @Amitava Mallick What problem are you trying to solve by doing this? I am asking as you note using sprints, which may indicate your team is using Scrum and sprint planning to decide what to work on each sprint. If adding a label to an issue can alter that plan, that may be a symptom there is a problem with backlog…

Hi @Shea Petricek -- Welcome to the Atlassian Community! Yes, and...to the suggested solutions from Brant, Alex, and John: these all would seem to meet your use case. One advantage of the automation rule is that it can send targeted emails, by assignee, for their specific issues. (The same can be done if you get each…

Hi @Charu Takkar -- Welcome to the Atlassian Community! Please try adding this to your JQL to find the non-archived ideas: "Idea archived[Dropdown]" IS EMPTY Kind regards, Bill

Hi @Darwin -- Welcome to the Atlassian Community! As your field is multiple-select, the smart value is a list of values. Try using an iterator to walk them, for example here is the list of mentions with comma delimiters: Hello to the points of contact: {{#issue.Point of Contact}}[~accountid:{{accountId}}]{{^last}},…

Hi @Anastasia Seidaridi Would you please clarify what you mean by they work for you and not for others? What do you observe? What type of projects are these rules running for: company-managed, team-managed, or both? For a question like this, I suggest posting images of your complete automation rule, including the…

Hi @Emma Hecht Yes, and...to Trudy and John's information...If you search the community you will find lots of attempts to implement this use case to work in rules. At this time, I believe the only work-arounds are: * use a bunch of if-conditions statements with hard-coded dates * write your own REST API function to do what…

Okay, this isn't pretty and I suspect it will get the "value" for a the field_name of "Name". Please reuse, as needed, and substitute each specific field's name for each usage. {{webhookData.audit.changes.match(".*(\{.field_name.\:.Name.*\}).*").match(".*value.\:.(.*).\}")}} How it works: * starting at the "changes", look…

Hi @Erin Quick-Laughlin You appear to want to change the structure of the response within the scope of the rule, and I am unclear how that is currently possible. The closest you may get is with match() and regEx to access the fields. To save you time...created variables and list filtering may not help with this use case…

Hi @Rohan Swami With the upcoming changes to supporting sharing custom fields between team-managed projects...and that JPD is apparently based on team-managed projects...do you anticipate impacts to the JPD project when the sharing is released? Thanks, and kind regards, Bill

Hi @Gabriel There appear to be at least two open defects for that symptom, which you may watch/vote for here to see progress: https://jira.atlassian.com/browse/JRACLOUD-76961 https://jira.atlassian.com/browse/JRACLOUD-73640 (Work is in-progress to fix this one!) Kind regards, Bill

Maybe that is it...or it is a rounding thing caused by diff() and number representation. Created variables sometimes work with functions...and sometimes not. You can try it to learn if they are supported for this case. For example: * create a variable named varNow set to {{now}} * use the variable in the expression as:*…

Hi @chengcheng zhang -- Welcome to the Atlassian Community! You cannot query issues that way with JQL. It is not a SQL and so does not support such dynamic calculations on fields. Some possible work-arounds depend on the frequency you need to do this and your desire to spend money/time: * Need this infrequently: export the…

Hi @Petri Ryhänen Smart values are name, spacing, and case-sensitive...and I noticed in your condition you use issuetype rather than issueType, and so that condition may be collapsing to null. Please try {{destinationIssue.issueType}} And also...what type of project is this: company-managed or team-managed? If team…

Well done, and... When using that syntax for ROUND it takes a value and a precision: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/#Functions Please try this: {{#=}} ROUND(({{issue.I score}}/2) + ({{issue.F Score}}/2), 0) {{/}} 

Thanks for that information. I have not used a Chrome browser extension to link issues in Jira before, so my ideas are based on general rule/Jira knowledge... When you look at the issue with the links, do you see the other types of links and the issue history reflecting link-types which do not appear in the trigger…