Bill Sheboy Expert

Well, that is how I expected the mapping to look for lots of NextGen projects shown on one board. Let's try to build up from one team: * Create a new filter for just one of the NextGen projects, ignoring the assignees and issue types for a moment: project = myNextGen_1 * Set the sharing of the filter as you expect for your…

I cannot enter defects for this tool, so I submitted this as a suggestion here: https://jira.atlassian.com/browse/JSWCLOUD-20928 Please take a look to add additional details and repro steps. Thanks!

Hi @Carter -- Welcome to the Atlassian Community! I saw an item in the public suggestions backlog about commit messages with commas being interpreted as a delimiter, and so turned into a list. You could check if that is happening with the line breaks by logging/adding a comment for {{commit.message.size}} to see it returns…

Hi @Mikaela Bertucci Rather than using a "false sprint" to organize the work items for stakeholder review, have you considered using Components or Labels to indicate things like "Discuss with Stakeholder A"? You could then create filters (and quick filters) for the Component, or Label, still ordering by rank, and move them…

Thanks, @Emily Thraen Would you please also post an image of the columns layout? I am interested if there are any status values which have issues, and which are not mapped. And, are the product teams only using Task and Sub-Task, or perhaps also Story with Sub-Task too?

Thanks for that information and ideas. I'd encourage the teams to chat about why there is a perception that "users are not on top of their deliverables". Even though there is a decision to use the reminder approach, the teams may uncover what is happening and help them use the pull-model of "your work" areas be more…

Hi @Julio CRUZ I am curious, what problem are you trying to solve with reminders? The need for reminders could be a symptom that people on teams have too much work in progress (and so it gets lost in the noise), and/or they have multiple locations/ways they track work (making what is next/important less visible). Best…

Hi @David Younger What problem are you trying to solve? Knowing that will help the community provide better ideas to try to help. In the automation rules, changelog does not support the Sprint field, so I believe you could only check for a field change of Sprint, but not that it was previously empty. Best regards, Bill

Hi @Marc Pincince Have you tried to use and If/Else structure to check the field for non-empty before the copy attempt? Best regards, Bill

Hi @Karanpreet Kaur Is the flag (impediment) the only way you indicate something is blocked? If so, and if you have the automation rules for server, you could do the following: * Add 3 custom fields: StartBlockDateTime, EndBlockDateTime, and TotalBlockTime (a number field) * Add an automation rule, triggered on a change to…

Hi @Sulaiman Abdullah -- Welcome to the Atlassian Community! As you are currently a paying customer, with access to support, I recommend you submit a support ticket to get an official answer rather than one from the community: https://support.atlassian.com/contact/#/ After you switch to the free version, the community…

Hi @William Vancrey My answer to your question is based on using Jira Cloud, not on any documentation. If someone can find documentation on LexoRank (Jira's ranking algorithm) which explains the behavior, please chime in. Settings and Context are key when ranking new issues: * First, ranking must be enabled for the board…

Hi @Ben Roye -- Welcome to the Atlassian Community! I haven't seen that before, and I just tried it and see no issues. Have you tried other browsers or to clear your browser cache to see if something is glitched? It appears your workflow has some required fields to set based on the transition to "fixed". When you try to…

Hi @Gonzalo Benitez de lugo If you mark the appropriate answers to this question as Accepted, that will help others in the community find solutions faster. Thanks!

Hi @Susan Hamilton -- Welcome to the Atlassian Community! I have seen that error for fields because of permissions or when the user-friendly name doesn't match the smart value. For the second case, I suggest using the REST API to grab an example issue to determine what the name of the smart value is, and then try to use…

Hi @Mike Bowen Have you investigated the automation rules for Jira cloud and the service desk? I suspect that they can do many of the things on your list. And you may be able to automate the remainder using the REST API. Here is some information on the automation rules for you to review:…

Hi @Adriaan Peeters -- Welcome to the Atlassian Community! For triggers like Version Created, the smart value {{version.name}} contains the triggering one. When you use the action to create issue, select Choose Fields to Set, and select Fix Version. Then type in {{version.name}} and when prompted to use the smart value,…

Hi @Nick Kight Do you have the automation rules add-on for your server instance? If so, you could probably build an automation rule on a scheduled trigger that would calculate the percentage completed. Best regards, Bill

Hi @Siddharth -- Welcome to the Atlassian Community! As you noted, it is generally not helpful to change the estimates of story points once the sprint as started or completed. Rather, the team could consider during the retrospective what happened (or they did not know) that led them to later want to change the sizing.…

Hi @Alexander Dowding -- Welcome to the Atlassian Community! Have you checked in Project Settings > Features > Code to see if that option is enabled? Best regards, Bill

Hi @Hector.Hood I just checked the public backlog and didn't see any open defects for this, and I suggest you submit a ticket to support here: https://support.atlassian.com/contact/#/ Best regards, Bill

Hi @lisbeth.olofsson One way to solve this would be to create a new Kanban board for read-only usage where: * The filter spans all possible projects with dependencies * The board's columns include (map) all relevant status values. Consider simplifying the columns if the source projects' boards use very different status…

Hi @David Loszewski What problem are you trying to solve? For example, are you trying to set up a scheduler for a rule on a cadence such as "the 3rd Thursday of every month"? If so, please look over the documentation on scheduled triggers and the use of Cron expressions:…

Hi @Nitin Mehta I do not believe this is possible with out of the box Jira; there is only basic logging reports. Several marketplace vendors may suggest add-ons to do further reporting... Or, if you search the community forum for things like time logged report you will find several posts listing those options. Best…

Hi @Mateusz Slifirczyk -- Welcome to the Atlassian Community! My experience and best guess is that clone's adding issues happens asynchronously, and so there is no guarantee of the sub-task (or other child item) ordering when added. There is an open suggestion to fix this for the server version. I couldn't find the one for…

Hi @Addam -- Welcome to the Atlassian Community! Would you please post an image of what you are seeing? When I use swim lanes, I am able to click on the grouping (parent) story, and the fly-out panel appears. Only when I turn off swim lanes, and just see the parents above sub-tasks, do I see the greyed out items. Best…

Thanks, and I am glad you figured it out. __Bill

Hi @Zoe Barr -- Welcome to the Atlassian Community! You noted that you have some plug-in products for Jira. Have you investigated the vendors Cumulative Flow Diagrams tools (or approximations of CFDs ;^) of the plug-ins? One of them may support changing from counting issues to counting other measures, such as estimates,…

Hi @Виктория You are showing an image of one board. What was the filter of the other board and what did it change to? Best regards, Bill

Hi @Micaela Barros -- Welcome to the Atlassian Community! As you are using Kanban practices, I would not recommend using "blocked" as a status/state in your workflow (or on the board's columns). That will drive up work in progess (WIP) count, lead the team to believe blocking is a normal practice, and discourage resolving…