Bill Sheboy Expert

Sounds like progress is being made! How are you trying to accumulate the story points, and when would you do so? Often this is done when an issue completes, or when a sprint completes. Then the Lookup Issues action is used with JQL to gather all of issues to sum:…

That is correct for Jira Software project, timelines. Here is the suggestion to add that feature, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-18677

Well done! Did you remember to set the Sprint field to the one from the trigger with: {{sprint.id}}

Hi @Carly Mojica Those are two different products and project types: The first one is a Jira Software, company-managed, Kanban board, showing the Timeline view. The second one is a Jira Work Management, company-managed, board, showing the Timeline view. For a comparison from Atlassian, please look…

Hi @Jennifer Maurer First thing, I am using Jira Cloud, and so my suggestions are based on what I know about automation, in general. With that out of the way... I believe you may set that field using advanced edit with JSON, in the "More options" section of the Edit Issue action. To learn more about such edits, please look…

No worries; we are all learning new things all the time. That lookup for smart values with {_} is a relatively new automation editor feature, and certainly does not list all possible smart values. It even has typos for some of them. And my understanding is it is not dynamic; it is static and based on another version of the…

I do not believe it is possible to change the type of the built-in "Story point estimate" field from numeric to anything else. If someone has created another field with the same name, that will certainly cause problems. I recommend pausing to learn why they added another field. Until then, first use this how-to article to…

Hi @Ari Robinson -- Welcome to the Atlassian Community! That is not possible with the built-in features of JQL for filters: it cannot compare 2 issue fields in a query. As workarounds, you could: * investigate marketplace apps which add features to JQL / Jira, * create a filter subscription for issues created daily and…

Hi @Ri A Yes, that is possible with Jira automation rules. Such a rule could trigger on Sprint Created to create and add the issue to the sprint. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @John Block 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 @Walker Heflin Yes, and...to Dave's answer: It is possible to call the REST API and get the required fields for an issue create: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-createmeta-projectidorkey-issuetypes-issuetypeid-get and…

First back to your original question, would you please post an image of the audit log for the case when the rule worked as expected? That may clarify what is happening. Can you manually move an example Subtask to "On Hold" on your board, or in the issue views? For your follow-up questions... Each team-managed project has…

Awesome; I am glad to learn that helped! What was the root cause of the problem?

Hi @Ariane Cannenburg -- Welcome to the Atlassian Community! The issue type, field, and other configurations are distinct for each team-managed project. A couple of possible workarounds for this scenario may be: * use export / import* export all issues with their fields for the source issues, including some uniquely…

Hi @Santosh Subudhi -- 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…

Hi @Fede B. Without seeing your rule specifics, I believe that is possible. For examples showing custom data usage, please see this article on calling the Jira REST API endpoints from a rule using the Send Web Request action:…

Hi @Robin Specht First, some ideas to fix the rule symptoms and then a simplification... By default, the actions of one rule do not trigger others. When you want the actions of one rule (e.g., your support project rule) to trigger other rules (e.g., your development project rule), the downstream rule should enable the…

Hi @hasungjoo -- Welcome to the Atlassian Community! First thing, I am not using Confluence automation rules, and so my suggestions are based on what I know about automation rules in general. With that out of the way... I do not believe there is a "lookup pages" rule action to use CQL to find the pages, and so identify the…

Hi @Tihomir Nikolov _Nemetschek Bulgaria_ I believe that solution approach will inaccurately average over time. For example, let's assume the ratings were 1, 2, and 2. Using the rule shown the averages over time would be: * rating is 1, and new average is 1 * rating is 2, and new average is (1 + 2) / 2 = 1.5 * rating is 2,…

Hi @Leonie Kemnitz As the rule editor shows, the syntax for your JSON expression is incorrect. Perhaps try this, assuming your custom field id value is correct: { "fields: { "customfield_10001" : "your team id value" } } Kind regards, Bill

Hi @John 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. Thanks!…

Yes, and...as I noted originally: all data for all linked issues (i.e., parent, subtasks, and linked issues) is not loaded for each issue a rule accesses. Instead the workarounds of branches, lookup issues, or REST API calls are needed to get at the information.

There should only be one field named "Story point estimate" in your team-managed project, and it is numeric. Regarding your earlier expression, assuming that customfield_10236 is your "Story point estimate" field: {{issue.customfield_10369.plus(issue.customfield_10236)}} That will only produce a number if customfield_10369…

Hi @Configuração Infinity System -- Welcome to the Atlassian Community! Have you recently changed your personal notification settings for your Jira profile? Have you confirmed the automation rules are still running? Have you confirmed with your Jira Site Admin if either the rules or email notifications are over the service…

Hi @Dipen 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. Thanks!…

Hi @Neil Womack -- Welcome to the Atlassian Community! After you clone the issue, add a branch to Most Recently Created Issue before the Link Issue action. That will change the context to the new issue, rather than the trigger one. * trigger: issue created * action: re-fetch issue (I recommend always adding this action…

Hi @Shiyao Ling -- Welcome to the Atlassian Community! Did you confirm there is only one field by that name, Last comment text, in your team-managed project for the different issue types? For the trigger issue's type in that example, did you confirm the field was added to the views? To help confirm both of those, please…

Hi @Chris Lucas According to the original announcement, to make such fields available setting the context to global should work: https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Announcing-the-ability-to-re-use-global-custom-fields-in-team/ba-p/2209113 Unfortunately it needs to happen for each project, and…

Hi @Sagi Gueta Is this a company-managed or a team-managed project? You may find that information at the bottom-left of the page expanding area. I hypothesize this is a team-managed project and that the id values for the statuses are different for your different issue types, such as Story and Subtask. With the condition,…

Hi @Sean McConell -- Welcome to the Atlassian Community! One way to do that would be to use Lookup Issues with JQL and an ORDER BY Created DESC clause, and branch using JQL to just the first item by the key to close it: key = {{lookupIssues.first.key}} The reason I suggest inverting the ORDER BY and using the first one is…