Darrel Jackson Rising Star

What I've opted to do is do a JQL search for each custom field to ensure there are no issues where the field IS NOT EMPTY. Then I've moved the custom field to the trash so if it does turn out to be needed the team have 60 days to say so. I've only done ones where there are no screens assigned. Thanks for your help. This…

Great, thank you. I think that was what I was looking for: confirmation that the JSM out-of-the-box ones are marked as LOCKED so I can safely delete other custom fields.

A few comments: * Calrification: For project audit, you need to go to Settings > Projects > Manage Projects in order to view when issues were last updated. Going Projects > View all projects doesn' tgive you the last updated date. * Is there a way to determine if a user group is in use (i.e. is assigned to project…

Really liking this change and a long time coming. Looking forward to it.

"The fact this article even exists is proof that the system provided to set this up is non-intuitive and therefore bad UX." I disagree. The tool is general purpose and quite powerful. Many customers have varied, specific requirements. There are many ways to solve different problems and these discussions are worth having in…

I raised a support ticket on this and support have found a better workaround. Add a "Re-fetch issue data" step to the automation rule and it will fire after the Epic Link is set.

That’s a fair assessment. It would be nice to have the option though.

Rank is a unique sort. Any sort after Rank won’t have the effect you’re looking for. It’s a bit like sorting by Key then sorting by something else - once you’ve applied the first sort the subsequent sorts don’t have any effect. You could sort by priority and then by rank. Priority and Rank are effectively doing the same…

To provide a more concrete rationale... imagine that you start a piece of work in one sprint that is 40h long and you complete half of it by the end of the sprint. You need to finish it in the next sprint so when you're planning do you assume it's still going to take 40h or do you plan for the remaining 20h of work? I get…

Yes, I think those are the best workarounds based on current limitations. I'll raise a support ticket to see if AR can be fixed/enhanced to do the issue creation and the setting of the Epic Link in one step.

That's good to know, thanks.

...the swimlane for Teams is possible for Kanban boards in Company Managed Projects as they are defined with a query (though you'd need to rely on the suggested team) Do you set "Base Swimlanes on = Queries" then write a query per Team? (e.g. "Team = 28"). This does work but is quite fiddly as a) you need to look up the…

Well, I get that calculating velocity for the team isn't straightforward so I wasn't expecting AR to do that. But I was only expecting to track velocity per team not per team per plan.

Yes, looks to be a different issue.

Thanks for confirming.

I get the answer and it seems like a reasonable design choice. However, I can't see this documented in the Jira Cloud AR documentation and it's the first question my users asked of me. I did see an article for the Server version which mentioned time zone issues in a round-about way. Correct me if I'm wrong and you can…

Perfect, thank you.

Can I get a bit more help? I've supplied a CSV file with just the Issue Key and Summary fields plus the new field I want to load. I've left the Summary field blank. I've trialled it with just the header row and 1 issue. I do the import but it doesn't update the issue. 2021-02-01 00:53:19,589 INFO - Import started by…

Beautiful, thank you.

Looking at the admin guide it says: "Importing a CSV to update existing issues will reset columns to their default values if they are not specified in the CSV." I was intending just to use Key and Summary plus the fields to be updated to avoid unintended updates to other fields. Does this mean I need to include every field…

Great idea, exactly what I'm looking for. I'll try it.

In the Create Issue screen in the top right there is a Configure Fields button and in the next dialog there is a "Where is my field?" link. That will tell you why the field doesn't appear on the form.

By default Kanban boards sort by Rank (i.e. top of the list is top priority). So you don't need to maintain an explicit Priority field unless you are managing priority outside of a board (e.g. you have an external incident/defect management tool which is used for prioritisation). If you definitely need an explicit Priority…

If you really must you could use issue links but these have poor visualisation and maintenance. Only do this if you have a small number and don't need visualisation. But probably not worth the headache.

It's not advised to rename the Epic issue type. Lots of stuff breaks. There are plugins to minimise what breaks but not supported in Cloud as far as I'm aware. Jira works with a 2-tier system, (ignoring subtasks that is) with multiple tiers using Advanced Roadmap. But that 2nd tier is always named Epic. If you're trying to…

One approach is to have them work in the same project. Then if you need to assign issues to one team or another you create a custom field with a team name drop down. You essentially virtualise the project for two teams. The downsides: * The project configuration is shared between the two teams so they need to follow the…

Worth pointing out you need Jira Premium to use the Advanced Roadmaps function. In Jira Standard it's not available.

Wow, that's really cool. I learned something today :) I never knew you could have non-"Done" statuses in the last column and it will treat it as "Done" from a burndown perspective.

Does the Sprint Burndown chart report off issues in the final column of the Sprint Board? Even if those statuses aren't in the Done statusCategory? Or does it report off issues in the Done statusCategory? I always assumed the latter. Would be good to know for my own knowledge.

Yeah, I think technically it would be mapping the "Verify" status to the statusCategory "Done". This is fine as long as no one else is using the "Verify" status in other workflows as an "In Progress" statusCategory. Jira thinks it's "done" which I think is fine for the team given "...there's no more for us to do for the…