Kelly Arrey Expert

Thanks @Mikael Sandberg 

What @Nic Brough -Adaptavist- said - use a single-select field to chose which board a given ticket will show up on. In the days before Advanced Roadmaps, when there was no "Team" field in Jira, we created a single-select field for the Dev Team, and mapped the Dev Team values to Jira groups of developers. This makes it…

I haven't tried this but can you create it outside the if/else block and then set in inside?

Hi @Fuadilah Mulyadhien, This isn't enough information to solve the problem. The original error message referred to the rule actor (which is not necessarily the same as the rule author) not having sufficient permissions to perform the transition. So, * Who is the rule actor? That's in the rule details * Do they have the…

@Shashank Aman If you're trying to add some TestFLO fields to the second screen, try typing "TestFLO" in the Field name box at the bottom and see what comes up.

Another idea is to create a new custom issue type and call it "Milestone". You can decide what fields you need for a milestone, and create Milestone tickets and include them in your plan.

Jira Kanban boards have supported backlogs for several years.

42.

"(status = "DONE” AND updated < -5d) AND (project in (10014)) AND (updated >= -13m)" I think the problem with this string is that there is a double quoted string ("DONE") within another double quoted string, so Jira thinks the "(status = " is your string and isn't sure what to do with what comes after it. You don't need…

This is great! Thanks for acting on our feedback!

Hi @Eric Percival, the way I understood your question, I think you'd want to add a new condition inside the branch, e.g., Trigger - When:issue transitions From: Dev on Deck To: In progress Condition - Project = GPS (This is the software project) Branch - For linked issues (All link types) Condition - Project != GPS Action…

Just came across an article that may be relevant to this topic: The SPACE of Developer Productivity

Hi @Jane Deese We use Structure by Tempo to implement our extended hierarchy. We've found it to be a little more flexible than Advanced Roadmaps in our context. There's some detail on how we did it here. The default Jira hierarchy is Epics -> Stories -> Sub-tasks. Here's an article about renaming the Epic level to Feature…

Hi @Sean Saxon glad that helped. To be clear, a "transition" in Jira is how you move an issue from one "status" to the next. The "validators" and "conditions" are part of the "transition". You shouldn't need a post-function. What we do in situations like this is to specify a "screen" on the transition which includes the…

Here's an example of a similar rule from Atlassian's Automation Template Library: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/115366

Ok, that's two of us stumped :-) It may be time to call in Atlassian Support. In my experience they're pretty responsive if you have Cloud Premium.

I'm on Structure Cloud, and this syntax was accepted: SUM#children{storyPoints} but this syntax was not: SUM#children{"Story Points"} Hope this helps :fingers-crossed:

Hi @Breanna Williams , I'm with @Sean Saxon on this one. Every issue has a Created date. You can complicate this with automation and additional fields, but if all you want is to calculate how long from requested to completed, just use the Created date.

Hi @Sean Saxon Can you view the Done transition in the workflow? It sounds like it has a Validator or a Condition that's testing for a field value, and giving a rather uninformative message if it doesn't get it.

Hi @Doug Myers On Jira Cloud (hopefully it's similar if you're on Server/Data Center): * Open the Filters pulldown in the top menu bar * Select Advanced issue search * Build the filter to get the list of issues you want* You can try this is Basic mode or Advanced/JQL mode - even Advanced/JQL mode is pretty straightforward…

Hi @Lara Sousa, I agree with @Jack Brickey , one would have to be very careful about how to act on what one observes from these reports. The implied assumption is that each team member's "productivity" is independent of the other team members. But we know that in an effective team, team members help each other, and the…

But it seems that "Training Records" is not a valid value for the "Project" field in your Jira instance, so I think you'll need to figure out what project you want to query, or investigate whether your Jira instance has two fields named project.

Augh!!!! I had a typo in my response to you. My apologies. Try: `Project = "Training Records" and "Training Date" = startOfDay(-1Y)` Sorry about that.

Hi @Colectivo Verbena There seem to be quite a few on the Atlassian Marketplace.

Hi @Sana Farooq Do you have "Asia/Karachi" in your time zone pulldown? 

Hi @Sunny Gupta I may be missing something here, but it sounds a lot you want want to add comments to an issue. This function is built into Jira and doesn't require any plugins. This is explained here.

Here's an example rule: And here's the output:

Try `Project = "Training Records" and "Training Date" - startOfDay(-1Y)` * JQL doesn't recognize Training Records as a project name without the quotes * Similarly JQL doesn't recognize Training Date as a field name without the quotes * Don't forget the Y in "startOfDay(-1Y)"

Hi @Sharif Alsughair What are you expecting to see in the other segments of the pie chart?

Hi @Jeanne ROBERT No, sorry, I'm not aware of any way to do that.