Bill Sheboy Expert

Hi @Jon Smalley Yes, and...to Nic suggests: IMHO, JQL has some challenges but it seems consistent in the area you note. When in doubt, please try something like this to confirm your query matches your desired outcome: * build your query up piece by piece, testing as you go * start with what is "true" for every issue you…

That seems like something is not passing/using your intended permissions. I have not used Forge for calling the REST API yet, so you may want to search this community or the dev community to diagnose that error: https://community.developer.atlassian.com/

Hi @Ibraheem Alqutub -- Welcome to the Atlassian Community! Are you are using a team-managed project and cannot see components? If so, components are not available for that project type. Here is the suggestion to add them, which you may watch or vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-17601…

Hi @Hadas Hamerovv You note getting errors with the PUT; what errors are you seeing? Knowing that will help the community to offer you ideas. Also, I note in your example using Transition ID that you are passing the status ID for it. Is that a typo? If not, please identify and use the transition ID instead, which you may…

Awesome; I am glad to learn that helped you. __Bill

There could be several reasons, and I recommend asking your site admin to try the Field Helper to uncover the reason: https://support.atlassian.com/jira-cloud-administration/docs/use-the-jira-admin-helper/

Thanks for clarifying; * there are overlaps between your standard Sub-task sets (e.g. Registration), and * when you change Task types, * you want to add/remove the delta changes, and * have them appear in the desired order Correct? If so, the only way I am aware of to do that would be to delete (or abandon/complete) the…

Hi @louise.simmonds Would you please explain what you mean by "it's causing a knock on impact of not providing the workload by assignee feature in the sprint backlog"? I just re-checked a team-managed project which uses Story Point Estimate, and selecting a single person for assignee in the backlog view correctly rolls up…

Please move the first to the end; this makes it apply to the returned list from the match(): {{issue.description.match("([a-zA-Z0-9_.+-]+@[a-zA-Z0-9-]+\.[a-zA-Z0-9-.]+)").first}}

Hi @Jace Proctor -- Welcome to the Atlassian Community! You are correct that the basic roadmap uses Start Date and Due Date fields in the issue for the epics. Please ask your site admin to add the field to your views if you cannot see it. For a team-managed project, I believe you can do that yourself without the admin.…

Hi @gjuffer I hypothesize that is from how the email is put as markup in the description. So if it is returning a list, you could get just one value by adding .first or .last to the end of that expression. Kind regards, Bill

Hi @Anish Taneja ! I do not believe automation rules have that capability for Data Center/Server. (With Cloud, this would be easier to solve :^) The challenge is for a trigger (or branch) that once you select the "batch" option, the issues are treated as a set...I believe. So if you put the condition inside of the branch,…

Regarding ordering, as sub-tasks are created over time the issue keys will increase. So key order matches created order. For your next question, would you please explain a bit? Are you asking how to find if a sub-task exists with some criteria, and when not found add one with that criteria? If so, you could use Lookup…

Thanks for that info! Based on your findings, you could branch with some adjustments to your rule. Please try this to see how it helps: * trigger: pull request merged * branch: on JQL, changing myProject to your project project = myProject AND issueType NOT IN (Story, Epic) AND development[pullrequests].open = 0 * *…

Hi @[deleted] Whatever solution you select to remind/force people to put in the comment, it may be worth pausing to consider "why do this comment" and to have a conversation with the team about the value of commenting. Otherwise you might not get the "value" you need, and it could lead to unintended consequences, such as…

Hi @Calvin Hawkes -- Welcome to the Atlassian Community! What type of project are you using: company-managed or team-managed? You may find this information at the bottom of the left-side, panel. I do not believe team-managed projects have the sprint report:…

Hi @Irina Jansone -- Welcome to the Atlassian Community! The first determination of what appears on a Jira board is the board filter. What is your current board filter, as that is what you will need to update? You may then reduce the viewed issues with quick filters, board sub-filter, swim lanes, etc. Kind regards, Bill

Hi @Ram Kumar Subramaniam -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? I note in one of your comments that you asked about having multiple status values for issues in a "backlog" condition. For a team using Kanban methods, I am unclear why that would be; that seems to indicate…

Thanks for that information! I still cannot see the bottom of your rule (after the branch), so I am guessing that the problem is: * because the trigger is selected to process a batch with JQL, and * the branch is on one (current) issue, also with batch selected... * that you are getting multiple emails (due to the branch).…

Hi @Vanessa Marie Delfin The index used in getFromEnd() is relative from the end of the list. I just tried this again with my test rule, and when I use: * {{issue.comments.getFromEnd(2).body}} -- I get the third from the end, no matter how many comments exist * {{issue.comments.getFromEnd(1).body}} -- is second to last *…

Hi, @Anish Taneja Would you please post an image of your complete rule? That may provide more context to help figure this out. Thanks! I wonder if this is some side-effect of selecting that batch processing operation at two scopes: the trigger for the rule and in the branch. The image should help determine that also.

Would you please post an image of your global/multi-project rule, including an image of the detail section? I could just be a settings thing. Thanks!

Sorry, I am not currently set up to test this rule with a build pipeline...My understanding was that trigger fires for each issue associated to the PR. Is that not the case you are observing (i.e. it is firing only once, and not once per issue)?

Hi @Joshua Hopkins Yes, and...to what Alex suggests, please look here for other formats if you need something else: * https://support.atlassian.com/jira-software-cloud/docs/smart-values-date-and-time-functions/#Smartvaluesdateandtimefunctions--- *…

Hi @danielmaycock What do you mean by "flag"? If you mean the "add flag" feature for issues, you may toggle that in an automation rule based upon the conditions you define. Just set it to "true" or "impediment". For your use case, you may want to try a scheduled trigger rule with JQL based on your conditions. To get you…

Hi, community! Thanks for this training idea. When interested in facilitating often, perhaps consider an improvement progression to develop your readiness/effectiveness to support others: * find a coach for yourself on this topic/area * learn about a method * participate as a team member; self-retro to learn * participate…

Hi @Ignacia -- Welcome to the Atlassian Community! I note in your screen grab that there is an error icon by the JQL branch. Did you define the JQL for the branch? If not, you could probably move the JQL from the condition immediately below it to the branch, and then delete the condition. Or, move it above as shown in this…

Thanks, Christine! I know how I would answer, and want to learn the ideas from others' perspectives. __Bill

Hi @Marrianna Martinez -- Welcome to the Atlassian Community! Automation rules and timing with Jira events can be challenging to reconcile. Would you please post an image of your rule, as that will provide some context. Thanks! Until then...How are you creating sub-tasks? Normally the issue is created and then its…

Yup, definitely a possibility. I wonder who the {{initiator}} is in the case where Jira does the comment after the resolve/close. Perhaps try that and log it for a test/experiment. If it is not a person, you could skip the re-open using a condition check.