Bill Sheboy Expert

@Aleksandra did you also remove the extra Story Point field from your card settings? Normally when the estimation statistic is "none" the story points display where you were seeing the hyphen. Thus the extra field on the card would not be needed.

Hi @Mohamed Riza _ServiceRocket_ As a reminder, this approach will alter the "Selected for Development" status/column to be an "in progress" condition, and so alter Jira reporting. Normally for a team using Kanban that status is not considered in progress. Kind regards, Bill

Thanks for that information, Manon. It appears the manager has a misunderstanding of the purpose/use of story points. Please consider having a conversation with the manager to help them understand this tool. And...As the manager wants information about effort costs, it may be more helpful to use time and calculate costs…

In your compare, please replace currentUser() with {{initiator}} currentUser() is a JQL function which works from the UI when I logged in user runs a query/dashboard. And {{initiator}} is the person user who performed the action that triggered the rule.

Hi @Ross Ramsay -- Welcome to the Atlassian Community! Yes, that is possible. Please look at this example in the documentation for a how-to: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CHANGEDCHANGED Kind regards, Bill

Hi @Sergei Gridnevskii I do not believe it is documented what order the values are returned in the fixVersions list, so first and last may not be what you want. Please consider looking at the list functions to get the min/max by release date and then using list filtering to target the exact one you need. Kind regards, Bill

Hi @Matthew Finch You seem to be co-mingling a couple of ideas here, so let's try to split this up a bit... You note a need to better see over-due versus other work items. If we assume you are using the Due Date, you could create a swim lane filter which moves those issues to the top of the board, such as: due <=…

Hi @Julia From what you describe, you want the person who commented for the comparison, correct? If so, please check with {{initiator}} for the person who triggered the rule. Kind regards, Bill

The started rule is easy: if a child starts work start the epic. For the completed rule, did you check all the children before moving the epic to completed? Thanks!

Looks like you found it before I posted again! :^)

Matthew, if you look at the bottom of the board settings > general page, do you see anything entered for the Kanban board sub-filter? If so, try clearing that filter's value.

Some ideas for possible readers of this article: Process Lead Time (also known as Process Cycle Time): the time from when a work item enters a process until it exits. For example, from when a customer makes a request until delivery is made to the customer. This is measured in units of time. Cycle Time: a measure relative…

Hi @Raoul Kaiser Short answer: you cannot do a nested query like this with out-of-the-box JQL Longer answer and work-arounds: What you could do instead depends upon frequency of need, costs, effort, and scope: * Need this often and for the entire instance* please check your instance to learn if you have any marketplace…

Hi @Samantha Mireanu -- Welcome to the Atlassian Community! Please try this one, substituting in your project's name: project = myProjectName AND statusCategory = "To Do" ORDER BY Key Please note that if you are using a team-managed project, there is no way to query yet for the difference between "to do" in backlog versus…

Hi @Matthew Finch -- Welcome to the Atlassian Community! A couple of other things to check for this symptom are: * Under board settings > columns: are the status values you expect to display mapped to the columns on the board? * Under board settings > general: is there a board sub-filter which is restricting display of…

Hi @Aleksandra This appears to be a board item for a company-managed project. Is that what you are using? And, which field are you entering your values in: Story Points or Story Point Estimate? Story Points are used by company-managed projects, and Story Point Estimate is used by team-managed projects. Kind regards, Bill

Hi @Lisa Zanini With the simple workflow you describe, you could build tracking for this yourself with automation for Jira rules rather than purchasing an addon app. And, you could decide how you want alerting/reporting to work. For example, perhaps you just want to remind the team that something has moved backwards,…

Hi @Petr AST Reading the documentation, the automation team indicates their regular expression parsing is "based upon Java's Pattern class", but no where is it fully documented what automation does and does not support for regular expressions. I recommend experimentation with a simple, manual or scheduled triggered rule to…

Hi @Gabriella Szeltner Adding to what Marco suggests... That error is telling you that your rule is accessing issue fields (start date and status) but the scheduled trigger has not supplied any issues. To fix that, you need JQL to find your issues, such as the following to find the issues planned to start this week. You…

Hi @Agata Puchalska -- Welcome to the Atlassian Community! I respectfully suggest another alternative to the solution you note: * Your team has a workflow, which you are visualizing with the Kanban board * Some times, work items (Jira issues) start into progress and then get stuck (which you are calling "parked").* This…

Hi @sixcorners Yes, and...to what Mark notes: Please post an image of your rule to provide context, and... You seem to indicate that this rule uses scheduled JQL and that it edits the issues as part of the rule processing. If the rule does not change any fields which result in excluding the issues from the JQL for future…

Hi @Daniel Brvnišťan I do not know of specific open suggestions for this, so you may want to make one which addresses your needs. However I do remember seeing a post from the roadmap team about a code-a-thon experiment to allow dynamically shifting those dates based upon a dependent issue change from the roadmap. They were…

Hi @Perla Miranda -- Welcome to the Atlassian Community! There is no loop counter yet, and how about a work-around to do this? The following works if you are using Jira Cloud, as you will need the action Create Variable. Essentially this creates a string of XCount characters long, and uses it to create the iteration…

Hi Sharona, I was noting Automation for Jira (which is built into the Cloud version). Please look here to learn about it: https://www.atlassian.com/software/jira/guides/expand-jira/automation If you can base your calculation on fields in an issue, you probably can write a rule to compute the value with a rule. It could run…

Hi @Bilal Mustafa -- Welcome to the Atlassian Community! It appears you are using Jira Server/Data Center, correct? If so, you may want to work with your site admin to contact support for an error like that: https://support.atlassian.com/contact/#/ For Cloud, I have only seen posts for that error as an intermittent…

Hi @Kaj Sennelöv Please try to save your labels from the parent in a created variable (varParentLabels) as this: {{issue.labels.asJsonStringArray}} Then when you edit the child to set the labels, you may use this: { "fields": { "labels": {{varParentLabels}} } } If that still does not work, please post an image of your…

Thanks for clarifying, Monica. That built-in report uses the board filter, or the filter you specify. For whichever is used, you could copy/update the filter to see the issues in advanced search by adding to the filter's criteria: AND resolved IS EMPTY

Hi @Monica Collins Do you mean the Average Age gadget on dashboards? If so, I believe that gadget accepts either a board or a filter, so you could copy the current filter used and add criteria to only included unresolved issues for the second report. Kind regards, Bill

Hi @Eric Rosenfield It appears you are using a team-managed project, and that would explain what you are observing. For this project type: * Issues in the "to do" status could be in the backlog or on the board, as you show. I do not believe there is any field at this time to indicate an issue is on the board. There are a…

Hi @John Houser -- Welcome to the Atlassian Community! Based upon your hierarchy example image, you may instead want to use the Jira issue types: * Epic* Story* Sub-task Tasks in Jira are at the same level as Story and Bug (defect), and so can only be connected with links, as @Kristján Geir Mathiesen describes. Sub-tasks…