Bill Sheboy Expert

Hi @Reinhard Huber How is your Request Participants field getting set? Could you just disable that set? If not, you may instead use the More Options > Additional Fields in the automation rule edit action to clear the field with JSON. Please look here for information how to do that:…

Hi @Huw Lewis I do not believe you can do that with out-of-the-box Jira Cloud. There may be a marketplace add-on for purchase that can support that. As a work-around, you could try entity properties at a project level, with name/value pairs based upon the Component. These can be accessed with the REST API, automation for…

Hi @Crystal Lane -- Welcome to the Atlassian Community! You cannot do a query like that with out-of-the-box Jira. You can probably do this if you have purchased a JQL marketplace add-on, like ScriptRunner. You can definitely do this using Automation for Jira (free or paid version) to write a rule to perform the check.…

Hi @david-urban Please try this one: {{issue.customfield_10048.emailAddress.value}} I have seen a few posts where the custom fields required the use of "value". And if that does not help, would you please post an image of your complete rule and audit log from an execution? That may provide some context for the community to…

Hi @James Mack -- Welcome to the Atlassian Community! My guess would be "not yet", as this idea is in the backlog as a suggestion: https://codebarrel.atlassian.net/browse/AUT-1031 Best regards, Bill

Hi @zakathuria Sorry, I wasn't trying to discourage you from trying this dashboarding. Please ask what you wish. I was noting that with so many measures, your team may get overwhelmed building those and then trying to respond to them. Think of a hypothetical example where you get a new electronics device with no user…

Yes, that is correct. The pipe symbol defines a default value when the operations leads to null. Seems like a good defense for counting operations.

Hi Alex, Regarding execution time, until we have more profiling information in the tools to confirm our understanding...the posts and documentation seem to indicate three trouble areas to watch for: * Re-fetch * Branching leading to asychronous processing (more than one issue) * And use of JQL in general Also, I just noted…

Thanks for that screen image, @katie.kurty Some follow-up questions... You note two code review columns on your board, First Code Review and Second Code Review. Which status values are mapped to those columns? Your rule shows a trigger from In Progress to Code Review. Later you check if the status is FE First Code Review.…

Thanks for the write-up, @Alex Koxaras -Relational- Great work improvising! Here is my suggestion to add more fields to Lookup Issues access, however it seems to have moved to the dust bin of "future consideration": https://jira.atlassian.com/browse/JRACLOUD-75018 And, here is a suggestion to make Created Variables…

Hi @katie.kurty -- Welcome to the Atlassian Community! Would you please post an image of your automation rule(s) and the audit log from executions? That may help the community give you ideas by providing more context. Thanks! Best regards, Bill

Hi @Glazner_ Dave _TR Commercial Excellence_ -- Welcome to the Atlassian Community! Are you using Company-managed (formerly called classic) or Team-managed (formerly called next-gen) projects? * For Company-managed, the Sprint Report has that information * For Team-managed, the Sprint Burn-down Report has that information…

Hi @Monica Li Are you trying to call the REST API for Jira Server to do this? If so, please take a look at this method in the documentation: https://docs.atlassian.com/jira-software/REST/7.3.1/#agile/1.0/board-getAllBoards Best regards, Bill

Hi @dave Just a guess: are you using any Next-Gen projects in your instance? If so, the status model seems have to "altered" the behavior, making WAS unreliable. Here are the defects for this: https://jira.atlassian.com/browse/JRACLOUD-70797 https://jira.atlassian.com/browse/JSWCLOUD-21154 Of note: this broke add-ons we…

Hi @Jonathan Aspeling How about this approach: * Lookup Issues on one of the counts you need with JQL * Save the count {{lookupIssues.size|0}} in a Created Variable * Repeat steps 1-2 for as many counts as you need * Create your email, referencing the created variables If you need the specific details for each lookup in…

Hi @zakathuria Yes, and... to what @Chris Buzon suggests, I recommend you pause and have a discussion with the team about that information as it seems like quite a lot. Specifically, "what would you do/improve/act differently right now if you had piece of data <X>?" If you cannot answer the question please consider if you…

Hi @Siddhant Modi It appears that you posted this same question as both a discussion topic and a question, so I am posting the other link here to help the community align the ideas they give you: https://community.atlassian.com/t5/Jira-discussions/Does-sprint-burndown-chart-update-when-I-switch-between-to-do/td-p/1659922…

Hi @pavlova_iryna Back in November 2020 when I last tried this feature, it worked as suggested by support, and apparently no longer works that way in my site instance either. I suggest asking your site admin to submit a support ticket for this issue here: https://support.atlassian.com/contact/#/ I did several tests for…

Sounds like a good idea to try. Please consider talking to the team about practices for pausing work; they may decide that moving to a different status (out of "in progress") gives you the information needed to help with forecasting.

Hi @Faraz Haider -- Welcome to the Atlassian Community! You could perform this type of check using: * a global/multi-project scope automation rule, * a Lookup Issues action with JQL, and * an advanced comparison condition on a return count of zero: {{lookupIssues.size|0}} However please note: it appears you are on the free…

Hi @Heather Reid The syntax that @Kian Stack Mumo Systems suggested above with an advanced compare condition should work for server or cloud: {{issue.comments.last.body.length()}} Check with your site admin if you can get the free version of Automation Lite added and then you should be able to do this. Here are some…

I am glad that helped. And...I would expect that chained removal to be a bit slower, and "maintenance unfriendly". ;^)

Hi @Daniel Ballinger The function remove() gets rid of one character. Maybe try replaceAll() instead using a regular expression: {{issue.Unit/Site Name.replaceAll("([0-9])","")}} Please look here for more information about that function, and the reference to regular expression syntax:…

You may want to check on Stack Overflow, as there are some examples and gotchas for removing styling elements with RegEx. You could also get close with RegEx, and then use the automation rule text functions to remove/replace remaining elements. Please post what you learn as others in the community will no doubt be…

Hi @KrishnaP I believe "Issue Links" column will produce both the outward and inward links in the export. However, this works the same as the other one-to-many and many-to-many fields, producing: * One column for each linked issue and... * One column for each linked issue of each type Regarding column order changes in an…

Hi @Marc-André Full disclosure: I am not actively using the DevOps triggers at this time, and based on what I understand about them, I wonder if you could... * When the pull request trigger fires the rule, it has the {{pullRequest.title}} * As you note the title contains multiple issues, you could parse those issue keys…

Hi @Paul Isaacs -- Welcome to the Atlassian Community! How about this work-around: Create a quick filter for the board which checks for resolution data after some reasonable time-frame. resolutiondate > -100d When you run the report, select that filter to exclude the older stuff. Update: I just re-read your question and…

Hi @Antonio Prioletti How do you know using the Jira issue data that work has paused? Or that it has restarted? If you have a way to identify and quantify that for an issue, you may be able to do this with automation for Jira (A4J) rules. Please look here if you are interested in experimenting with that approach: *…

I am glad you got it to work! Good job, Atlassian Support team! Makes me wonder if that custom field was ever created with another type, or is shadowing a previously and similarly named field. Hmmm... One could observe that some aspects of automation for Jira are a tad under-documented at this point. (e.g. when can custom…

Hi @Megan Olney Reading through some other posts on this symptom, it appears a few things could cause this. Please consider trying/investigating the following: * Try clearing your browser cache, closing, and then re-opening the browser. Then try to move issues again. * Check if the board/project is using ranking, as that…