Bill Sheboy Expert

Hi @Paulo Amaral No, that is not possible with built-in features. As a work-around, I wonder if you could write (or find) a REST API function to call from the rule which would diff the values, providing what you ask. Kind regards, Bill

Hi @Sheri Widler I do not believe there is anything built-in to do that for dashboard gadgets. Perhaps look at the Atlassian Marketplace for gadgets that have this capability: https://marketplace.atlassian.com/search?category=Dashboard%20gadgets&hosting=cloud&product=jira Kind regards, Bill

Hi @Abhishek There are many community posts for this scenario, such as the ones listed under the "Related Community Content" on this question's page. Please take a look at this one as an example: https://community.atlassian.com/t5/Jira-Software-questions/Summing-up-story-points-from-Linked-tasks-to-story/qaq-p/2448964 And…

Curiously...subtask CORE-48 shows as Resolved and in a status of New.

Hi @Dan Tombs What is your definition of "tech debt" in the context of this post? Kind regards, Bill

Hi @Beth Wilkinson I wonder if there is another rule running which is doing this. When you look at the history for the subtasks, what/who does it say is moving them to Done? Kind regards, Bill

Hi @Matt Feetham -- Welcome to the Atlassian Community! I believe you would need to read and parse the issue history for that information. Kind regards, Bill

Hi @Tiele Declercq That match() function result is an array, rather than a list. So the work-around when this happens is to strip off the square brackets with chained, remove() function calls, followed by a split() to create a list. Storing your original parsing into a created variable can help with this.…

Please try that in the assignee field when creating the subtask.

Hi @Neil Williamson -- Welcome to the Atlassian Community! When the trigger issue for a rule is changed in the rule steps, that happens in the cloud. But the remaining rule steps continue to use the issue's fields as they were from the time of triggering. (i.e., the original values) When you want the updated values, add a…

Yes, and...I hypothesize this is the start of consequences for having multiple fields named "Story Points". I recommend discussing this with your Jira Site Admin so they are aware of the situation and can take actions, as necessary.

Hi @Shahbaz Iqbal -- Welcome to the Atlassian Community! There is nothing built-in which provides those transition date/time values in a tabular format as you described. The information is stored with the issue history for each item, and it is not easily accessible. The built-in control chart report provides a way to view…

Hi @Raphael Fernandes That is possible in an automation rule, although it is a bit complicated... Let's assume your Jira board uses a filter based on ORDER BY Rank ASC, which is the default sort order to allow drag-and-drop of issues on the board. And so the thing you need to change is the Rank. But Rank (also known as…

Please try to assign the subtask at the same time you create it, in one action. That can be done by typing in the smart value in the field, it will appear below the field, and then it can be selected: {{myApprovers}}

Hi @Mourad Siala Beyond the scope of your question...Please consider using the issue "flag" feature (or other Jira feature) to indicate blocking rather than having a status for that condition. In my experience, when teams add "Blocked" as a status to their board, they are accepting "blocked" is a normal condition rather…

Awesome; I am glad to learn that helped! Please consider marking this question as "answered" as that will help others in the community find solutions to similar needs faster. Thanks!

Hi @Maycon de Souza Leal What parts of the other examples / information did you not understand? And, did you look over the information I provided in the other thread on advanced branches? To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @Lana Kelly Yes, that seems possible to do with automation rules. As to whether this can be done "elegantly" that may be subjective, based on your ideas :^) I recommend you outline when (i.e., the triggering events) when you want the values quantified and summed. For example, when a field changes, a child issues is…

Hi @SandeepSingh R That seems possible to implement with an automation rule. And... Using automation requires learning and experimentation. I encourage you to try to create the rule, and if you run into challenges, post images of your rule and the audit log details, describe what is not working as you expect, and the…

Hi @Harsh What problem are you trying to solve by synching these two fields when they appear to have the same value? Would using just one value work? Kind regards, Bill

Did it not add them as a hyperlink to the issue? Perhaps check the markup needed for sending a message to Teams.

Hi @Maycon de Souza Leal -- Welcome to the Atlassian Community! First thing, please consider creating a new question for something like this. Otherwise only the people following the older thread will see it. You can also link back to earlier posts for context. Thanks! Do you have a rule started? If so, please post images…

Hi @Lea Casper Did you try using the Edit Issue action, selecting the Flagged field, and leave the value empty? That should clear the value. Kind regards, Bill

Hi @Test work Please review the suggested solution as you appear to be missing the part to use an advanced branch to iterate over the values. As an alternative, I believe you may also try adding them in one step using advanced edit with JSON. Kind regards, Bill

Hi @Beth Wilkinson -- Welcome to the Atlassian Community! There are two things to check for this symptom... First thing: smart values are name, spacing, and case-sensitive. The one for the Lookup Issues action is this: {{lookupIssues}} So perhaps change your Send MS Teams message to try that. Next, are there any issues in…

Hi @Sujitha.Krishnan Is this for a company-managed or a team-managed project? You may find that information at the bottom-left side of the page expanding area. Company-managed projects use the Story Points field, and team-managed ones use Story point estimate...even though they are both called "Story Points" on the screen.…

If you side-by-side compare the issue not displaying and the clone of it which is returned by the query, what do you notice for the following fields: * Created * Project * Epic Link * ...and the issue history for any changes to the Project and Epic Link since the issue was created

Ah, I got it...Your rule is triggered on Field Updated, for status. And (surprisingly to me) that rule is triggered on new issue creation! In this edge case, {{fieldChange}} contains the bean as this is moving from "no where" to your backlog (or another status). The hint of this is the "from" is "new". IMHO, this is a…

Hi @Audrey Tolman -- Welcome to the Atlassian Community! First thing...your question seems related to this thread, but by posting it here only the people following this one will see it. Please consider creating a new question, and linking to related ones. Then those following newer posts will see it rapidly. Thanks! For a…

Jira Product Discover (JPD) projects appear to be based team-managed projects...with a lot more features and views. And in my experience all the basics of automation rules worked with JPD projects. Certainly there are opportunities for Atlassian to add more automation features, tailored around JPD-like features :^) Until…