Bill Sheboy Expert

Hi @Оля Соловей -- Welcome to the Atlassian Community! You appear to be using the free license of Jira Cloud, and so are using the Basic Roadmap feature. On this version, epics are displayed based upon the Start Date and Due Date. There is nothing built into the roadmap to handle shifting those dates based upon late…

Hi @Nouf.Alshabanat Short answer: this 50 limit appears to be built-in, for users and drop-down fields, so there is no apparent work-around Longer answer: There is an open defect and a couple of suggestions to remove this limit, which you may watch to see progress/updates: *…

Hi @Ankuskum Yes, and...to the question from Thomas: what problem are you trying to solve by doing this? If such unlogged edits were generally possible in Jira, it would break the history of issues, making the log of changes worthless. You could never rely upon it when you needed it. I wonder if you have a different need…

Hi @Petr AST I am curious: how long are your sprints such that 7-days notice prior to the end helps with completion? What problem are you trying to solve? Let's say your sprint is 2-weeks in duration. Waiting 7 days may be too late. Perhaps observing the board daily during the daily scrum would help stay on track, with a…

Hi @Nic Brough -Adaptavist- Thanks for your response, and for the diligence you and your colleagues apply. With no other responses in the last week I will accept your answer to close this one: there are no defined review/evidence checks other than what a poster chooses to apply. That would explain the content I see in some…

Hi @Sunil kumar As you and @Fabian Lim note, Jira Data Center's version of automation rules does not have the lookup issues action. Instead you have the bulk processing feature, which may be used with a scheduled trigger or branch using JQL: https://confluence.atlassian.com/automation/bulk-handling-of-issues-993924653.html…

Hi @Ingo Mohr Yes, you could do this for specific status values or generically (with statusCategory). I encourage you to experiment and try both ways to learn about automation rules. For example as generically, ignoring issue status: * trigger: issue transitioned (status values do not matter) * condition: issue type is…

Hi @Ethan Stein I believe you are correct that the only way (currently) to do this in an automation rule is to call the REST API with a web request, and parse out the options from the response. Without seeing your rule to understand your use case, I wonder about your second paragraph: The reason I need it is so I can feed…

Puzzling that still doesn't work; still gotta be the branching. I can think of one other way to try this: Get rid of the branch on the created variable, and try to update directly by forming the JSON using list functions. First, create a new variable, named SIJson, with the value from your first branch, instead of {{SI}}…

Markku, would you please post an image of the chart to help clarify what you are seeing? Thanks!

Hmm... Would you please post an image of your current, complete rule, and of the audit log from an execution where it only adds some of the values?

Argh, branches! :^) Okay, branches which process more than one issue are executed asynchronously, and there is no guarantee of when they will finish...so, your writes may be walking over each other as the loop progresses. Let's try this: in the branch, after you make the edit to add the value, insert a Re-fetch action.…

Sadly, not yet. I recall this is due to the differences in the way company-managed versus team-managed projects like epics to their child issues... And I remember seeing a suggestion on this for company managed. That probably will not be addressed as there is an in-progress suggestion to add multiple boards for…

Hi @Matthew Hardy I do not believe there is a built-in dashboard gadget which can sum up a custom field like that. You may want to investigate the marketplace for app purchases: https://marketplace.atlassian.com/ Given what you describe, consider looking for tools which allow multiple operations (sum, average,…

Hi @Cengiz Oner -- Welcome to the Atlassian Community! Short answer: there is nothing in out-of-the-box Jira Cloud that can display that report Longer answer: The closest built-in thing to this is Atlassian's interpretation of a Cumulative Flow Diagram (CFD). However that correctly shows issue counts, not total of other…

Hi @James Wardle That scenario seems related to these two open defects: * https://jira.atlassian.com/browse/JSWCLOUD-16302 * https://jira.atlassian.com/browse/JSWCLOUD-21917 Please watch/vote for those to see progress. If you believe your scenario is different and you are on a paid Jira license, please ask your site admin…

Hi @Magda Biskup Some of the things you note are unclear, so please let me know if I misunderstand you use case. * You have 3 projects' information and want to show them on one Kanban board * You do not state if all 3 projects are team-managed, company-managed, or a mix of types * I assume: you created a filter combining…

Hi @Anton Prokhozhy One challenge with what you are trying is that your team *could* decipher what a JQL expression is supposed to do, but open defects may prevent that expression from working. So maybe try some "beware this" queries which combine information from company-managed and team-managed projects, such as status…

Hi @Abby Domanowski Yes, and...to Gareth's suggestion: First thing, I am using Cloud version and so cannot test this... * You are correct that Data Center version of automation does not have Lookup Issues. Instead you can use the the bulk handling feature of the scheduled trigger or a branch. * In that case, this might…

Let's try some specific things to see if one of them reveals what is happening. * Is the rule triggering? If so, please post an image of the audit log showing the details. * If not, please change your trigger to Field Value Changed on the Story Point Estimate field (not Story Points) * Next, please add an audit log entry…

There wasn't a work-around listed with the ticket. Perhaps try using the JSON edit features and set the field ID to the exact value of the priority you need: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/

Thanks, and... Company-managed projects use "Story points" and team-managed use "Story point estimate". Please try using the other field in the edit with lookup issues. And also...Smart values are case sensitive, and lookup issues uses camel-case like many of the values : {{lookupIssues.Story point estimate.sum}}

Yes, now that you have confirmed that {{SI}} contains a comma-separated values (CSV) list of the data you want, change the Advanced Branch to use: {{SI.split(",")}} That will convert it into a list which is then input to the branch.

Thanks for the additional details, Kristie. Based upon above, you have resolved your question, correct? If so, well done!

Hi, Mehgan! Your scenario *can* work with 2-3 rules, and it has some risks to handle: such as an endless loop (runaway) in rule execution. The key is to have a stopping or "breaking" condition to prevent a problem. You do not mention one thing: if the label changes in the Story, and cascades up to the Epic, do you expect…

Hi, Hari! Are you using a company-managed or a team-managed project? And, would you please post an image of your edit issue action? That may reveal what it is not summing as you expect.

Hi @Mehgan Hawk -- Welcome to the Atlassian Community! First thing: to get more people looking at your questions, please consider creating a new one and adding a link to related ones. Otherwise, often only the people already watching will see it. For your automation rule, are you trying to keep the epic and child issues in…

Hi @Maria Cristina Carreon Suarez del Real -- Welcome to the Atlassian Community! To do what I described: * Your site admin adds a custom field, such as "Abandoned", and disable the issue deletion permission. This can be done at a project level, as desired. * Teams update their board filters to exclude abandoned issues.…

Hi @Leila Nightingale Short answer: This is not possible with out-of-the-box Jira Cloud. The closest built-in tools are Atlassian's interpretation of a Control Chart and a Cumulative Flow Diagram (CFD). Longer answer: * That article about SAFe,--which is essentially rebranding common process measures of WIP, Age of WIP,…

Hi @brenda_banderschaper -- Welcome to the Atlassian Community! Which link do you mean? I tried both of the ones that I provided and they worked for me. In the old defect, there are several new posts about people seeing this problem, so I suggest if your are on a paid Jira license, to ask your site admin to submit a ticket…