Bill Sheboy Expert

Hi @Gabriela Molitoriszova Company-managed projects (CMP) use the Story points field and Team-managed projects (TMP) use the Story point estimate field. These represent the same thing (a relative sizing measure), but cannot be used interchangeably between types of projects. I am guessing you are using a CMP with a board…

Hi @Swati Mathapati -- Welcome to the Atlassian Community! When you note the rule is not working, what do you observe happening? What do you see in the audit log when the rule runs? Until we see that information...Two possible improvements to your rule could be: * only trigger the rule when your custom field is updated *…

Thanks for explaining, Kendall. I think Craig has you on a good path with their suggestion, as once the new bug is created you could use branching and perhaps JQL to go up to the story and then cross-link the bugs from the branch. One gotcha to watch for: applying the links in a consistent direction or duplicate links…

Without seeing your specific automation rule, I wonder if you can alter the trigger or perhaps add a condition on the {{initiator}} user to prevent the rule processing under those conditions.

Hi @EtienneSevin You could do this by instead branching on the JQL used in the lookup issues, or use an advanced branch on the keys found in the lookup. Kind regards, Bill

Hi @Raúl Eduardo Echeverría Urbina -- Welcome to the Atlassian Community! Did you copy that smart value expression directly from your rule, or retype it in your post? I am asking as you have some misplaced parenthesis and curly brackets, so perhaps check that. You could also do this using the dot-notation to chain the…

Hi @Grzegorz Ostrowski Adding onto Alex's answer: what problem are you trying to solve by doing this? Knowing that information may help the community to offer suggestions. For example, perhaps instead your rule could have a trigger/condition based upon the presence of issue data, and so eliminate the need to disable a…

Hi @Zac How many values/conditions do you need to check? (i.e. the number of cases leading to cloning issues) For a "simple" rule, I suspect that you would need nearly the same number of rule components, regardless of how you implement this: branch on current issue/JQL or if/else conditions. And FYI: there is a 60…

Hi @Kendall Sosnovich What problem are you trying to solve by linking the defects to each other...when they are already linked to the source item under test (i.e. the story)? Knowing that may help the community to suggest ideas to solve the problem. Thanks! Kind regards, Bill

Hi @will Writing automation rules is quite a bit about learning and experimentation. So...what have you tried thus far to solve this problem? If you post images of your rule, the audit log details, and what is not working that will provide the community more context to help. For example, are you stuck trying to…

Does it show an error in the audit log, not update the value, or update it with an unexpected value? If it is none of those, I suggest working with your site admin to submit a ticket to Atlassian Support, as they may see something in the logs indicating what is happening: https://support.atlassian.com/contact/#/

Hi @Esmeralda DeArmas What do you mean by: Is there anything we can do so they don't count against us for the sprint? You seem to be describing the team is working on items using the Scrum Framework, and those items have dependencies on people who are not on the team, leading to blocking situations, where…

Understood, and...Perhaps discuss with the delivery manager on their needs/the problem they are trying to solve with this type of reporting. That may help to find a solution to help. Thanks!

Pardon me if I was unclear; please try this to select the respective id values for the field: { "fields": { "customfield_11600": [ { "id": 847 }, { "id": 853 } ] } }

I am unclear why your displayName is not available. Two possible causes are that there is no {{issue}} at that point in the rule or that the assignee is Unassigned/null. Regarding your other question, this seems related so let's try addressing it here... And, I do not think that is easily possible with your rule. You…

Thanks for explaining how you imported the values into the list. I was instead asking the field's purpose/how you use it. Understanding that may help the community to offer alternative suggestions. Thanks!

Well done! You could also do that without the created variable by referencing the value directly as {{createdIssue.key}} Your version works because created variables are currently text-only, and the default smart value (field) returned for {{createdIssue}} is the key. In the future, I hypothesize that created variables…

Thanks, Owen. That is puzzling to me why distinct would work as that could potentially return multiple values while first can only return one. I am glad to learn you have it working...regardless of my confusion :^)

Hi @Nadya Domracheva -- Welcome to the Atlassian Community! You cannot compare different issue fields with out-of-the-box Jira Cloud features. Specifically, JQL is not a SQL and so does not have such features. Some possible work-arounds to solve this use case depend upon how often you want to do this and how much…

Hi @Gangadhar Dalli You have not provided any specific details about your use of the REST API and so it may be difficult for the community to offer ideas. Without that information, please consider: * reviewing the REST API information on rate limiting to learn if you have exceeded usage…

One idea is: consider accepting that "there are no best practices; only better ones." I find this simple idea helps clarify uncertainty is a normal part of delivery, experiments facilitate learning and improving, open-mindedness of others' views leads to better understanding/collaboration/opportunities, and realizing there…

Hi @Kathrin -- Welcome to the Atlassian Community! Atlassian's interpretation of a Cumulative Flow Diagram (CFD) draws the data based upon the currently viewed date/time range and filter. * So it only draws the bands correctly and in proportion to count/time when all possible data is displayed * As soon as you zoom in or…

Hi @[deleted] Yes, and...to Mikael's answer: You do not show your entire rule for context, and so the {{sprint}} smart value is only available stand-alone if the trigger was one of the sprint-related ones: sprint created, started, completed. Within an issue, the sprint field is a list, and so if your issues have been in…

Hi @Lorinda Quesenberry Yes, and...to Jack's answer... The difficult part of your use case is "following sprint", as I do not believe that is possible with out-of-the-box JQL. If you only check if issues were done, re-opened, and in an unfinished sprint, this could work: project = myProjectName AND status WAS Done AND…

Hi @María López There is nothing built in to do this. Have you tried adding one of the many free browser addons for scrolling screen print? Many of them allow saving as a PDF or image file. Kind regards, Bill

Thanks for that information. As I described above, you could solve this using custom fields to save the developer (or tester) when an issue transitions, and set it back as needed. The saving and reset could occur with automation rules. To get you started on creating your rule, please review this documentation and examples:…

Hi @Jeff Cadow he-him Context is important for automation rules, and so please post images of your entire rule and the audit log details. That will show which issue is being used as the source for adding the subtask, and what adjustments are needed to fix the symptom. Thanks! Kind regards, Bill

That appears to be a different field than you used originally: customfield_15300 Which one is correct, 15300 or 11600? Whichever one it is, you probably should use "id" with the numeric id value for the team.

Please note that currentUser() is not going to work in a scheduled trigger rule, as the rule actor is probably the Automation User and not a logged in person. If you need this to work for a specific user, please change the rule actor in the details. If you need some other behavior, please describe what that is. Thanks!

Awesome; I am glad you figured out a solution! What you noted about Move is one of the reasons it is quite tricky to do anything with that action (other than detect it) in an automation rule. There is just do much good stuff implemented in Jira that could require special handling in a rule: issue type changes, required…