Comments
-
Hi @Tom Meyer -- Welcome to the Atlassian Community! As I recall, you needed to identify a JIRA user for email-generated issues. Is that correct? If so, could you add a user condition to your rule that limits edits to only those issues created by this email-generated source user? Best regards, Bill
-
Hi @Rich Steenwyk I am glad to hear that helped. As the folks working on the rules have noted to the community, they are constrained by what the API makes accessible to the rules engine. There appear to be race track conditions to improve in this area to help consumers with rule execution reliability. Best regards, Bill
-
Awesome! I am glad to hear that worked and that the human-readable color names worked. __Bill
-
Ah, I just noticed you are are on Server and not Cloud. Please take a look at your available triggers to find what you could use to detect an update. Then you may be able to use a condition to check for a change to the Sprint value using the changelog smart value.
-
After reading the other comments in the other posts below, I can suggest one more thing to try, as this does appear to be an add-on and not a native part of JIRA... The vendor's comment indicates that they add and then update issues. If the sprint field is set on the update rather than on the create, that is what you would…
-
Hmmm... This sounds like the sprint field is not populated in this path. If you are using an add-on for that story map, consider checking in with the vendor's support. If not, hopefully someone else will see this question and comment. Sorry I could not be of more help.
-
Hi @Dan I haven't tried this, and apparently Code Barrel, who authored the rules, does this with webhooks. (Code Barrel is now part of Atlassian.) Here are some posts from them on consuming the webhooks:…
-
Thanks for that information. I tried this from the backlog (creating a story in a future sprint), and it both triggered my rule and logged the sprint name. I do not have any story mapping add-ons to test what you are seeing. I have experienced timing issues with the Create Issue trigger, whereby all of the data was not…
-
Hi @Pierre Heinrich I experimented and was able to get is to work using the custom field name representing epic color... * First, figure out the name of the epic color field using the REST API to query an example set of epics. Here is the how…
-
Hi @Sreerampavankumar Govindarajula -- Welcome to the Atlassian Community! What do you mean when you say: For some reason Automation trigger is not recognizing the sprint when I create the story in the user story map view sprint horizontal lane. Is the rule triggering, but the sprint field is empty? Or, is the rule not…
-
Sounds like an opportunity for a marketplace vendor to build a "time machine" for cloud...there are equivalent marketplace products for JIRA server and Confluence.
-
Thanks for that information, Doug. The {{issue.sprint}} is a list field, and the max function only works for the specific attribute, such as startDate. That is why I suggested using it for the condition test. Unfortunately, there is no way I can see with smart values to find the latest sprint in the list, and then use all…
-
Yes, and... I believe there is an execution limit for global rules, not the project-level ones. If you can put your rule at the project-level, executions appears to be unlimited, and there are other constraints:…
-
I am glad that worked for you, @Callum Carlile _Automation Consultants_ __Bill
-
Great; I am glad that is working for you!
-
HI @Stefan Salzl -- Welcome to the Atlassian Community! Would you please post an image of your rule? It seems from what you are describing that the rule is firing because the trigger occurs and then the condition stops processing. Providing the image will help the community give you more information and advice. Thanks, and…
-
Hi @Paul Brown Yes, and... to what John said: the newly created issue is the triggering issue. So try that and see if it works. Occasionally the newly created issue is not fully available at the time the trigger fires, and so copied fields do not always populate. The work-around for that is to add an action to Re-fetch the…
-
Hi @Callum Carlile _Automation Consultants_ Please try: status changed to "query raised" AFTER -1h Best regards, Bill
-
Hi Doug, These smart values work when trying to compare the changed issue the sprint: * {{issue.sprint.startDate.max}} This would be the start of the latest sprint. * {{issue.sprint.endDate.max}} This would be the end of the latest sprint. You should be able to compare these to the updateDate (or now) in the condition to…
-
Hi... I am glad that helped solve your problem. There should be a button up near your question to accept the answer. Best regards, Bill
-
Hi @Doug Levitt Looking at the smart values and triggers, my guess would be "yes", although I haven't tried it. It might look like this for added after sprint start: * Trigger: field value changed for sprint * Condition: {{now}} is greater than {{issue.sprint.startDate}} * Action: edit your custom field that you noted For…
-
Hi @Cristiano I was trying to use Create Variable, as you noted above, and I noticed a side-effect: When the JQL in the branch spans more than one issue, the repeated calls to Create Variable do not function as you note. Instead, each call appears to shadow the variable, and when the loop completes all of the loop-scope…
-
Hi @Omar Ali I think you are on the right track as this being permission related... First, confirm that they have permissions to see the dashboard itself. The gadgets seem to cache the filter used, so first confirm that the person has permission to access the filter by checking its permissions. If they see nothing, this…
-
Thanks, @Joe I hope that the smart value documentation will eventually centralize this information and align it with the REST API output. __Bill
-
I agree... Please post back here once you get a chance to try this, or mark the question as answered if it solves it. That will help others in the community find solutions faster. Thanks!
-
Hi @Daniel Reyzman As an update... We decided to implement our own Age Of WIP using a custom field and automation rules. Here is a how-to: * Add a number custom field, such as AgeOfWip * Add an automation rule to compute the value* Trigger: scheduled at your desired update frequency. For example, once per day. * Branch on…
-
HI @Rob C In addition to what @Jack Brickey suggests, there are some browser add-ons, such as for Chrome. I haven't had a lot of luck getting those to work consistently. There are several suggestions to add better board column control, including this one I wrote a while ago: Able to collapse columns on Kanban board…
-
Hi @Whisley Santos For the date, please try converting the time zone before formatting: {{issue.created.convertToTimeZone(reporter.timeZone).format("dd/MM/yyyy hh:mm")}} This example uses the Reporter's time zone, but you could hard-code it if you wish. Regarding the avatar images, doesn't look like that is possible. There…
-
Hi @Joe Please try the guidance below to find an unlisted/undocumented smart value, using the REST API to capture an example issue: https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/ Note that if this does not provide an exact match, it may get you close enough to experiment and find…
-
Hi @bruno_vidigal -- Welcome to the Atlassian Community! I suspect you are running into a timing issue for the create issue trigger. That is, the issue is not fully available to the rule logic at the time the trigger catches the new-issue event. I have worked around this condition before by putting a Re-fetch action…