Bill Sheboy Expert

Hi @Wendy Chen To do that, please use the accountId as referenced in that linked post. For example, when editing the auditor field you may type in this smart value, it will appear below the field, and then you can select it: {{issue.reporter.accountId}} If you want it from the trigger issue instead, and I believe you do…

Great; I am glad to learn it is working now!

That is curious...I just retested it and it worked for the Description field. If you are trying to get the data from the last comment to save, perhaps try this: {{issue.comments.last.body.remove("\\")}}

Awesome; I am glad you got it fixed!

Hi @Nicole Radle It is possible for a version create in one project to create another version in a different project. This would normally require a global/multiple project scope rule to allow the actions to span projects. You appear to be on the Jira Cloud, standard license level. If that is correct, please note there are…

Hi @Shannon Miller -- Welcome to the Atlassian Community! The issue created trigger can fire faster than the data is available...and without seeing your audit log details it is possible the condition shows the field as empty. The work-around for that is to add a Re-fetch action immediately after the trigger, and before the…

Hi @Aen Tan -- Welcome to the Atlassian Community! That symptom appears related to this defect which was just created today, which you may watch/vote for to see progress. https://jira.atlassian.com/browse/JSWCLOUD-23249 Kind regards, Bill

Hi @Aaron Pavez The backslash is the escape character so you need to double it for use in the expression. Please try this: {{issue.myField.remove("\\")}} Kind regards, Bill

Hi! Yes, that is possible with an automation rule. Basically you decide the trigger (e.g. adding subtask, editing the due date, etc.), gather the sibling subtasks, and grab the smallest date to use. Perhaps something like this: * trigger: issue created * action: re-fetch (this will slow down the rule and reload the…

Hi @Clément Berger It appears that work is in progress for automation, according to this item in the backlog. The description and history indicate copying attachments for Clone was implemented last month, although I have not tried this yet. https://codebarrel.atlassian.net/browse/AUT-1030 Kind regards, Bill

Please re-read the responses above; this rule can be implemented as you have described.

For company-managed projects (CMP) * Issue type epics currently have a field called Epic Name (which is a text field) * Issue types of story/task/bug have a field called Epic Link (which is a link field), and was used to connect them, child to parent Both Epic Name and Epic Link are deprecated and being removed. For the…

Hi, Alex -- Welcome to the Atlassian Community! CMP projects do not use the Story Point Estimate field, so I would advise not adding that to any screens for them. In the UX, Jira calls both fields "Story Points", and so that is clearly going to confuse matters. After you remove that unused field, would you please clarify…

Hi @[deleted] -- Welcome to the Atlassian Community! They are separate product subscriptions, and I believe the storage is independent, as described here: https://support.atlassian.com/security-and-access-policies/docs/track-storage-and-move-data-across-products/ You may check your storage by going here for your site and…

Hi @Lupe I am aware of no built-in features to inventory the saved filters by usage. There may be a marketplace app to do this, so perhaps look there first: https://marketplace.atlassian.com/ A much more labor-intense thing to try is to call the various REST API functions, repeatedly, to find references. For example, Get…

Hi @Leslie_Hernandez -- Welcome to the Atlassian Community! It seems your project has an existing automation rule, or script addon, running which is making the change to the parent Due Date. Please post images of your current rule and the audit log details, as that will provide context for the community to offer…

You have written the query to answer your 30 days question. If you change AFTER -30d to AFTER -15d you will have the other one. Again I respectfully suggest: please consider taking the free training for JQL which I noted in my first post. That will help you answer these and many other questions. Thank you.

The answer depends upon what you wanted to accomplish. With your addition, that query will ignore any issues created after 30 days ago.

Hi @Rahul Jith When you want the actions of one rule to trigger another rule, the second rule should enable the option "Allow Rule Trigger". This option is in the rule details at the top. Please take care using this feature. Poorly written rules could lead to run-away execution problems, which is why this rule option is…

Sorry, but I have no idea where you mean for roadmaps. My understanding is roadmaps currently displays the summary for company managed projects. I just retested with my company-managed project and that is what I am seeing.

Hi @Rahul Jith I am not quite following what you describe. Are you noting that an issue which was just created is being returned by the query? If so, adding a condition to check the created date should help. If not, please post your complete current JQL; that may indicate what is happening. Thanks!

Hi @Mo Sajjad -- Welcome to the Atlassian Community! There are built-in fields for that need, named Start Date and Due Date, which are normally available by default. Kind regards, Bill

Sorry, my mistake: that character cannot be escaped after all. And it seems it is ignored in searches as it is the exclude operator. Instead you would need to test for inclusion of desired things and exclusion of others, such as with: project = myProjectName AND summary ~ "\" Agreement\"" and summary !~ "feature" or this…

Thanks, Jakob. I just found this open defect that Move Trigger does not fire for this scenario: https://codebarrel.atlassian.net/browse/AUT-2161

Hi, Dom. As an FYI...everything in automation rules has the 100 issue limit: triggers with JQL, branches, and Lookup Issues. One work-around is to chip-away at a problem, 100 issues at a time, by marking issues so that they are not picked up by subsequent rule executions. e.g. by adding a flag/value so they no longer match…

Hi @Cole Marsteller -- Welcome to the Atlassian Community! Your assumption is incorrect. Only the board filter's ORDER BY determines order on the board, even within the columns. I believe the quick filters do not impact order. Kind regards, Bill

Hi @Steve Suranie It appears between your Project condition and first Created condition you are using an ampersand rather than the AND keyword. I recommend writing/testing your JQL with Advanced Issue Search first, and then using the resulting value from the browser URL in your REST API call. Kind regards, Bill

If your pages are all within one Confluence Space, you may be able to do this dynamically from your Components (if the names are aligned). I believe there are some community posts on doing this from a rule, so perhaps search for those. If that does not work from the Create Confluence Page action, I believe you could also…

Just to clarify the situation today for company-managed projects: * There are fields for Summary, Description, Epic Name, and many others * Summary and Epic Name are required fields when creating an issue of type Epic If you are seeing something differently, please post an image as that may provide some context for what is…

Hmmm...That field is a list so perhaps try this: fixVersion IN ( {{triggerIssue.fixVersion}} ) I believe that will default to checking the id value and change to a list when the trigger issue has multiple versions assigned.