Bill Sheboy Expert

Thanks, @G subramanyam Another free training from Atlassian to help PM and PO role people is this one: Gain Project Insights through JQL https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql Kind regards, Bill

You could replace your JQL condition on status changes to instead check with a User Condition for the person who triggered the rule, compared to your list. I cannot tell which version of Jira you have (Cloud, Server, Data Center), and so if you do not have the User Condition, you could instead use an Advanced Compare…

Hi @Shannon DeVico -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Thanks for that additional information on your scenario, and... As a disclaimer I am not using Premium edition and so cannot test some of the things I may suggest. If you have any of the marketplace addons which extend the features of JQL, you may want to check how they can help with such queries for the modified…

Thanks for that image, and FYI to try to stay in one thread when posting. That helps others see if there are multiple ways to answer a question. Your rule is branching to the parent to check the labels, and so the edit then takes place on the parent. And, as written, this will run for story / subtask pairs also. Are you…

Hi @Olivier Reuland -- Welcome to the Atlassian Community! Where are you trying this? If in an automation rule... Please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as…

How do you know which one should generate the email? If that can be determined from the issue fields, an additional condition will limit so only that one leads to the email.

Hi @Stephen Holtom -- Welcome to the Atlassian Community! For a Scrum board in Jira, issues must be in the far right column to be considered "completed" for the sprint. The status category has no impact. Please review your board configuration, and perhaps move that In Archive status to the far right column. Kind regards,…

Yes, that is correct. The outline of your second rule would be: * trigger: issue transitioned to Done * condition: issue type equals Subtask * action: send email I am unclear which comment information you want to send in the email. The most recent comment would be: {{issue.comment.last.body}} Please look here to learn more…

Your filter is using issueType = Task, but those are not Subtasks. The out-of-the-box issue hierarchy is: * Epic* Story, Task, or Bug* Sub-task or Subtask What you described earlier was looking for Subtasks, and so you may change that part of the query to: issueType IN (Subtask, Sub-task) However, you also now mention…

Hi @Hizkeel Khan I am not quite following your exact scenario...It seems you have an issue of one type (e.g. Story), and when creating another issue want to link that to the first issue and copy the Component field. That should be possible with an automation rule. Using automation rules requires learning and…

Hi @Jerrod Van You probably do not want to do those in one rule, because the subtask will move to Done later...after some time. Please try adding another automation rule, triggered on transition to Done and checking the issue type equals subtask, and then sending the email. Kind regards, Bill

Hi @Mohit Jain For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @박윤희 -- Welcome to the Atlassian Community! What is not working at you expect? Would you please post images of your filter results and the dashboard gadget, rather than a link to you company's Jira site? Kind regards, Bill

Hi @Sarah Edell I am unclear what you are asking; you mention both exporting automation rules and then details from issues like subtasks. Would you please clarify: what problem are you trying to solve? That is, "why"? Knowing that may help the community to offer suggestions. Thanks! Kind regards, Bill

I just re-tested this for an issue that I have access to, and was correctly prompted to download the attachment. If you go to the specific Jira issue for that attachment: * can you view the issue * can you download the attachment for the issue If you can, I suggest working with your Jira site admin to submit a ticket to…

First thing: when using the Issue Created trigger, I recommend always following that with the Re-fetch Issue action. This trigger can fire so quickly that the data is not available for later rule processing, and the re-fetch will slow the rule by about one second and reload the data before proceeding. You rule is using an…

Only people with Jira access (and access to the specific issues) will be able to view those attachments using the link.

Thanks for the screen images. I recommend trying to post the entire rule in one image, perhaps using a screen capture tool or browser addon for scrolling capture. That will ensure the rule pieces are shown correctly. Just to confirm your scenario, do you have 2 or 3 PMs from whom to select: * if only US selected* use the…

Hi @bzekich -- Welcome to the Atlassian Community! To find the subtasks of an issue, please try JQL like this, substituting in your story's key: parent = theStoryKey AND issuetype = Sub-task To learn more about JQL and creating queries like this, please see this free training from Atlassian and the documentation pages:…

Wow, that is good to know. Yet another reason for better validation of rules before publish succeeds: if the copy cleared some fields of the Send Web Request, it should fail to publish, preventing this symptom. That could be part of this suggestion I made a while ago: https://jira.atlassian.com/browse/AUTO-170

Hi Jim, Welcome to the Atlassian Community! As already noted, a workflow validator may be better for a scenario like this, and I see you describe why that was not used. Your rule is using a JQL condition on status and the user performing the change, at any point in time found in the changelog. That means if anyone who was…

Hi @Vicknesh Shanmugam -- Welcome to the Atlassian Community! Some things I have learned to build up knowledge, skills, and experience with retrospectives: * Observe other retrospectives* Watching how others facilitate retros can reveal what works for one team may not succeed with others, different techniques (or ways of…

Thanks for sharing your experience on this, @Leon Saw Regarding planning, session duration, etc. I treat things like one finds in the teamwork playbook like readiness for a larger retrospective or workshop: * have a plan in mind, with durations for the activities and outcomes to assess progress; and * have alternative…

Awesome; I am glad to learn that worked for you!

Hi @Fiona King -- Welcome to the Atlassian Community! That is possible, using an automation rule, with the Issue Assigned trigger and Manage Watchers action. How would you know the person did not add themselves manually as a watcher, so the rule does not remove them incorrectly? If you want to try to build your rule,…

Thanks for this information! The confluence-supporting tools look quite helpful; passing this one on to some other admins for a review. :^)

That is interesting! I am trying this with a Free license, and cannot edit a cascading, custom field using an automation rule, edit issue action's drop-down list. The JSON edit is the only option.

Hi @Dan Schetley Regardless of the way the issues are created, an automation rule would need guidance for the linking. If you are creating these with a scheduled trigger automation rule, the linking could probably occur there, either through absolute (e.g., a specific key and link type) or relative linking (e.g., link to…

Hi @Phil Bustin I wonder if the CONTAINS ~ operator and fuzzy search uses known words. And so to match on other things, try adding the wildcard character: "[custom field name]" ~ "SSR*" Kind regards, Bill