Bill Sheboy Expert

Hi @Jeniffer Kamaraj First thing, I recommend reviewing the free training and documentation from Atlassian on using Jira Query Language (JQL). That will help you learn / experiment how to create such queries faster and better support your teammates. *…

Please carefully re-read what I posted and Trudy's article... Trudy's article describes a scenario where a chain of work items are linked as "Blocked". And so as one work item's dates are changed, the dependent one is updated. The rule you show is not identical to that case: instead you are branching over all of the…

The history / changelog could still show you as the person making the change when a rule, workflow, or addon made the change. From the global automation list, did you check the audit log to filter by your work item key? That will show any rules which directly accessed it. If an addon / app performed the change, you may…

Hi @Marina Laysha and @Marc -Devoteam- I was able to reproduce this with a team-managed, project-specific custom selection field. This does not happen when adding a global / company-managed, custom selection field to a team-managed project. This change has the same recently added behavior as Labels (in all project types /…

Hi @Mathew Lederman Thanks for describing your workaround, and... After the endpoint call, it seems you are getting the last entry, and so a list function could be used rather than performing the math with get(): {{webResponse.body.last.name}} Kind regards, Bill

Hi @Angel Salazar Short answer: in my opinion, scenarios like this are quite difficult in Jira as it has limited built-in project-management features for cascading updates of a chain of work items. It may be better to investigate marketplace addons to Jira for such features. Assuming you are still interested in using…

Hi @Andreas Schaefer -- Welcome to the Atlassian Community! Your rule's JSON expression to update the value appears to be using a created variable which was never created. Please try adding that inside the branch and before the edit to calculate the value by subtracting the new worklog value. For example: * action: create…

Hi @Nathalie Strnad -- Welcome to the Atlassian Community! Based on what you describe, you may have an automation rule which is updating the fields. I recommend working with your project admin to check the automation logs and the work item history to confirm this, and why the rule is making the changes. Kind regards, Bill

Hi @Angie Allen You were able to post this question and it is in the Confluence / Questions area. And when I just checked your profile for posts, I do not see one posted elsewhere. Perhaps try: * clearing your browser cache, * close all browsers, * start one up again to log in, and * try creating the question again. Kind…

Hi @Karoline Ramos For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution *…

Hi @Jonathan Smith Most of the rich text markups and macros are not supported by the built-in automation Edit Work Item action. (This may be because rules appear to use version 2 of the REST API endpoints.) At this time, I believe the only workaround is to use Atlassian Document Format (ADF) and the REST API endpoint (v3…

Thank you for the additional details, @Mahriah Alf Earlier I noted the need to parse the Sprint values found, by work item, in the Lookup Work Items results. This is necessary because... * When a work item does not complete in one sprint, it might carry-over to the next one. And thus another question is: which sprints do…

Hi @Mahriah Alf -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log…

Hi @james_vanderhaeghe For a question like this, context is important for the community to help. Please post the following: * What problem are you trying to solve with this rule? That is, "why do this?" * An image of your complete automation rule in a single image for continuity * Images of any relevant actions /…

First, your branching is incorrect to use the Epic as the parent of the new Task. Please try this: * trigger: manual * action: create version * action: create work item (for the Epic) * branch: to most recently created work item* action: create work item (for the Task), setting the parent to Current Work Item as that will…

Hi @Boris Ahrendt -- Welcome to the Atlassian Community! This is a very old thread, and so I recommend creating a new question with the "Ask a question" button at the top of the page. Until we see your new question...Please note Atlassian is in the process of renaming "issue" to "work item", so look for the "Edit Work…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

@Beata Kupiec -- I am using the Pacific time zone (US) for this Jira site.

Hi @Gemma Huang -- Welcome to the Atlassian Community! This is a very old thread, and so I recommend creating a new question with the "Ask a question" button at the top of the page...perhaps including a link back to this thread for context. When creating your question, remember to include an image of the complete rule, an…

Hi @Eric Browning -- Welcome to the Atlassian Community! Rather than using JSON, you may enter the key for the most recently created work item (i.e., the Epic) when creating the Story in its parent field from the dropdown list: {{createdIssue.key}} Or, after the Epic is created, you may branch to most recently created work…

Hi @Salim Hammar You are using an a tool external to Jira. I suggest contacting the vendor's support via their marketplace page for assistance: https://marketplace.atlassian.com/apps/1224798/n8n-cloud?hosting=cloud&tab=support Kind regards, Bill

Hi @Michael Frade and @Trudy P Claspill I do not believe that is possible with the built-in features of AQL: as with JQL, the left-side of an expression must be a field / attribute and not the value of one. What do you want to do when a match to the condition is found? Knowing that may suggest alternatives. Kind regards,…

Thanks, @Trudy P Claspill as I misread the question to add additional links: not the "clone" link. Although the solution is the same: add the link when the work item is created or change the rule scope and use the separate action.

Hi @Melissa Mattee Murphy What is the scope of your rule (in the details at the top): single-project, multiple-project, or global? * All rules can create (or clone) work items into other projects. * However, a single-project scope rule cannot access work items in other projects for view or update...but linking modifies…

Hi @Eric Browning -- Welcome to the Atlassian Community! At this time, there is no date (or date / time) picker option for the Manual Trigger's user inputs. Here is the suggestion to add that feature: https://jira.atlassian.com/browse/AUTO-744 Until that is implemented, please add the toDate function to convert your text…

Hi @Lisa Gilmore I believe that edit window appears as a pop-up. Have you checked if the pop-up was blocked in your browser? Kind regards, Bill

Hi @Beata Kupiec FYI -- When I retested this morning with the same fields and same work items, the symptom no longer appears in the JPD list views. Thanks, Bill

Hi @Boris Ahrendt That is great news! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks! For your follow-up question... My understanding is once the rule actor changes, any actions the rule does will be shown as done by that actor...and not by the initiator…

Hi @Katrin Erhardt The rule you showed in the image has a single-project scope. That means the rule can create (or clone) work items into other projects but not access them in any other way. Please change your rule scope to multiple-project, selecting the relevant ones, or global, adding any conditions on project needed to…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!