Comments
-
Yes, I sometimes do.
-
Two suggestions to try: * Please write those values from your edits to the audit log to see if they have what you expect. * Try doing both of the edits in one action (selecting each field separately). That may prevent walking on changes...if that is a possibility for automation rules. Thanks!
-
I wish there was better/more organized documentation on smart values. Until that improves, it helps to read over all of the examples to learn what is possible. For example, here is the stuff on lists where you can see things like {{^last}} https://support.atlassian.com/jira-software-cloud/docs/smart-values-lists/ And also…
-
Thanks for that image. It appears Atlassian decided to use a different field name for the translated dialogue: Delivery Date versus Due Date. They are the same field. I am unclear what is happening to cause this, and when I tried this for a Basic Roadmap, something else displayed...not even including the current sprint! As…
-
Hi @Evan Nixon Yes, and...to what Darryl notes: If you expect there could be multiple mentions in the comment, I do not believe there is a built-in way to parse those values into JSON for the edit of a multi-value picker field. A work-around is to get your id list into a created variable, and then use list iteration and…
-
How about a "better" one rather than "best"? (I don't believe in best practices, only better ones than what are currently doing :^) * When pondering something impacting the team, "take it to the team".
-
I have heard this one inverted: "Scrum Masters are not happiness coaches".
-
Hi @Johnny FromCanada Would you please post an image of your rule structure (no need for the web request details) to clarify a bit? It is unclear from what you are describing by "if-branch" and "if-block": is this a single condition or an if/else component. So the scoping of the symptom you describe may be a factor.…
-
Hi @Mya.Hauck Would you please post an image of your rule as that will give the community context to offer ideas? Thanks! If you are setting the text field with the date, you may want to use one of the date format functions to get the exact format you…
-
Hi @Andrey Rudnev For automation for Jira, the only way I know to enforce the order of triggering for a set of rules is to: * create the conditions in the order you want rules to execute * and if you want one rule to trigger another, set the downstream rule's option to "Allow Rule Trigger" For #1, that means creating…
-
Hi @Masa Janezic Have you tried writing to the audit log the issue field for the comparison? I am wondering if there is some reserved character which is preventing the CONTAINS "~" from succeeding? If you manually try an advanced filter search with a value and your JQL, does your query work as expected? Kind regards, Bill
-
Hi @Niklas Zarnecke Is this for a company-managed or team-managed project? And, if they are: * using epics, * do not use the backlog, * do not use the epic panel, * and you cannot change the filter which is currently including epics, then * I do not know of a way to hide the epics from the board. All of the available…
-
Hi @Rory Gould -- Welcome to the Atlassian Community! You may do this with an if/else and "contains" checks on the field. For example: * trigger: issue created * action: re-fetch (to prevent timing problems) * if/else* field condition: summary contains "My Text A" * action: edit issue * else* field condition: summary…
-
Hi @Rahul Khanna If you are seeing the rule triggering in the log and the conditions not matching, this could be a timing issue where the data is not available at the time the rule fires. This can happen with the issue created trigger. To confirm/resolve this, please add a Re-fetch action immediately after the trigger and…
-
Hi @siond To remove the text for an issue, you could use the Replace or ReplaceAll functions: https://support.atlassian.com/jira-software-cloud/docs/smart-values-text-fields/#Smartvaluestextfields-replace-Stringtarget-Stringreplacement-…
-
Hi @Vanessa Marie Delfin First thing, I am using Jira Cloud and not Server/Data Center. Have you tried this syntax to see if the values are available: {{changelog.comments.last.body.fromString}} Kind regards, Bill
-
Hi @Stephen Solomon Good idea putting in the Re-fetch, as I was wondering if you are encountering a timing issue. You may still want to confirm if the transition is still occurring *before* the dialog appears and so is user-bound time for entering the comment. Regardless, in your email please consider treating the comments…
-
Hi @Michael Beatty -- Welcome to the Atlassian Community! A few observations to help: * When you have a rule that you expect to be triggered by the actions of another rule, look at the Details section of the dependent rule, and enable Allow Rule Trigger. Otherwise the rule engine detects a potential runaway/looping error…
-
Hi @Presten Swenson Yes, and...to what Trudy notes: there are already a few open suggestions and bugs on this symptom, including this one: https://codebarrel.atlassian.net/browse/AUT-2090 Kind regards, Bill
-
Hi @Alex Koxaras -Relational- What do you think about splitting the clone operation, to clone the template epic first and then clone the child issue? In that way, the child issues can be correctly linked to the cloned parent epic, using {{createdIssue.key}} As built, I do not believe that rule's clone action will re-map…
-
Mini, at this moment the only thing is to watch that defect to note any changes. Perhaps also consider if there is another way to query what you need without WAS on the status field see if that helps.
-
Awesome! I am glad to learn you got it solved. FYI for that list to build the string: you can also use conditional logic to not add the last comma, and so eliminate the need for the call to substringBeforeLast() {{#issue.Strategic Initiative}} { "value":"{{value}}" }{{^last}}, {{/}}{{/}}
-
Hi Ivan, I am glad to learn that helped. At this time I do not believe there is another way to add authorization; there are a few suggestions/requests in the Code Barrel (now part of Atlassian) backlog to add that feature. Kind regards, Bill
-
Sorry, I am unfamiliar with a "delivery date" controlling the basic roadmap for epics. My understanding is that it is only the Start Date and Due Date fields on the epics. Is this for a company-managed or a team-managed project?
-
Hi, Shelley! Just some quick follow-ups: * What kind of project are you using: business, software, or service? * And if software, are you using company-managed or team-managed? * And what type of board are you trying to use, Scrum or Kanban? Thanks!
-
Thanks for that information, Petr. For the sprint-triggered events, you can get at the smart values. But that often does help in use cases like yours; for that, a scheduled trigger with JQL on the openSprints() would be better to find and then access the sprint attributes. For the other case you noted (all tasks completed)…
-
Hi @Valerie Fischer I do not believe there is anything built-in for that parent/child branching yet. There are several open suggestions for it that you may watch/vote for: * https://jira.atlassian.com/browse/JRACLOUD-74105 * https://codebarrel.atlassian.net/browse/AUT-1779 * https://codebarrel.atlassian.net/browse/AUT-1789…
-
Hi @Shelley Sherman What do you mean by "child issues" of stories? Do you mean other sub-task types or something else? I believe that sub-task types of stories are the only issue types which have the built-in behavior you describe, moving on the board independently of their parent story. For company-managed projects,…
-
Hi @Michelle Walton -- Welcome to the Atlassian Community! I do not see any open incidents on the main status or automation status tracking pages for this symptom. If your Gitlab and automation rule configurations have not changed, please consider submitting a ticket to Atlassian to take a…
-
Hi @Kaline Leoni de Almeida -- Welcome to the Atlassian Community! Would you please confirm if you are using the Standard license of Jira Cloud, with the Basic Roadmaps feature? For that version, I believe the epic timeline is based upon the Start Date and Due Date, and not based upon the child issues' sprints. When I just…