Created vs Resolved dashboard for TMP

[Michal Klucz]

Hello,

I've just discovered that recommended Created vs Resolved dashboard is useless for my TMP as it's based on the resolution field, which is if I am correct NA by default in TMP.

Now, I can set up automation to set resolution whenever I transit from * to Done/Cancelled. but what was done in the past, it's lost (and we are talking about hundreds of issues).

Can this be fixed by bulk editing? or if I want to use dashboards, I have to migrate to CMP?

BTW this report is on the list of the suggested official reports so there should be solution to do that. : https://support.atlassian.com/jira-service-management-cloud/docs/what-are-custom-reports-in-team-managed-projects/

[Trudy Claspill · Accepted solution]

Hello @Michal Klucz 

The tags on your post indicate that you are working with a Jira Work Management project.  

But the page reference that you provided is for Jira Service Management.

What type of project are you actually working with? If it is Work Management, you will see navigation options horizontally across the top of the display, like Calendar, Timeline, List.

If it is Service or Software, that will be shown in the navigation panel on the left just below the project name. Example:

[Michal Klucz]

Hello Trudy, I am JWM for this project, 

[Michal Klucz]

however still got these reports in recommended section

[Trudy Claspill]

Yes, you are correct. I have not spent much time working with this type of project so have not previously looked at the Reports that are automatically listed for it.

The fact that the Resolution field is not set is a documented issue here:

https://jira.atlassian.com/browse/JWMCLOUD-180

I haven't searched to see if there is a corresponding issue about the report not working because of this.

The workaround is indeed to set the Resolution field using an Automation rule triggered by the transitions to "done" statuses.

For the issues that are already done, it does not appear that you can edit Resolution through the Bulk Change feature. However, you can use another Automation rule to set the Resolution field.

Use a Schedule or Manual trigger. Use a Branch/Related Issues/JQL action and supply a JQL for finding all the previously done issues in the project. Use an Edit Issue action to set the Resolution field.

Note that this will also cause the Resolved and Updated timestamps on the issue to be set to the current date/time. Unfortunately you cannot directly set those values so your report will show all those previously done issues being done as of today.

[Michal Klucz]

thank you! I will test it tomorrow morning, but I see that this is what we need right now, just to eliminate hundreds of tickets from the past that would totally ruin our reports otherwise.

[Trudy Claspill]

A final note.

There is a limit to how many issues can be operated on in a single rule execution. You may have to run the rule to update old tickets multiple times to get them all updated. So, include in your JQL criteria to only update tickets in the Done Status Category for which the Resolution field is empty.

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

[Michal Klucz]

Yay!! all done, finally see a green spot on the report@ 

[Nic Brough -Adaptavist-]

Um, no.  TMPs have resolution, it's just done by setting the "done" flag on columns on the boards, rather than setting the field directly.

If you don't have the resolution tick on at least one column in your board, create a new column to the far right of the board and drag an end-status into it.  A tick will appear in the header.

[Michal Klucz]

how can I set up a flag? was unable to locate a workflow settings in TMP (where I would expect to find it), I was sure this is one of the key differences

[Nic Brough -Adaptavist-]

Yes, they are annoyingly difficult to configure.

Create a new column to the far right of the board and drag an end-status (any green one) into it.  A tick will appear in the header.

[Trudy Claspill]

Are you sure that applies to Work Management projects?

[Nic Brough -Adaptavist-]

Yes, but only TMP JWM projects, I didn't test a software TMP project directly, but the last time I looked, they work the same.

[Michal Klucz]

this must be very complex or so simple I don't see that. any new column I create is a blue/in progress stage :/

[Nic Brough -Adaptavist-]

Have you dragged a "green" status into the new last column?

[Michal Klucz]

Hi Nic, I was unable to find an option to drag, however as soon as I wanted to reuse the name 'test' I got feedback that that name was in use so I have to change it in... workflow editor where I was able to assign the type of status to do/in progress/done.

is that what you were talking about?

[Nic Brough -Adaptavist-]

No.

In the board configuration, you can add a column, then drag a status into it.  Your screenshots are not of the config areas.

[Trudy Claspill]

@Nic Brough -Adaptavist- 

There is no board configuration screen in a Business/Work Management projects, whether then are Team Managed or Company Managed, unless I'm missing something.

[Nic Brough -Adaptavist-]

Yes, there isn't a config option. but JWM TMP projects set the resolutions automatically.  (With CMPs, we still have to go back to the workflow)

[Trudy Claspill]

I don't think that is true. I don't believe JWM projects set the Resolutions automatically.

In my experience with my Free instance, when I create Work Management project (Team or Company) and just use the available templates with no change, neither the Resolution nor the Resolved fields are set when issue move to "done" statuses.

Here are screen shots from a brand new Team Managed Business project I made from the Blank template. I created one issue and moved it to Done. Neither the Resolution nor the Resolved fields are set.

[Nic Brough -Adaptavist-]

Ugh, so Atlassian have made it even more broken by ignoring the "resolution is empty = unresolved" rule we've had for the last couple of decades.

I've tested with a few project types, some work, some do not.  That needs a fix.

[Trudy Claspill]

The fact that the Resolution field is not set is a documented issue here:

https://jira.atlassian.com/browse/JWMCLOUD-180

[Michal Klucz]

Hello All, 

Nick, Trudy is correct. There is no configuration option in JWM, so that's why I was confused when you asked me to drag a flag/colour. I know how to do that in other products, but I was unable to locate it here :) glad to have it sorted!

Then, Trudy is correct, in JWM the 'resolution' field is just ignored, and the Status field is the only field connected to the stage of the issue. And it would be great as TMP is supposed to be simplified and much less complex than CMP. HOWEVER... (and this is big however) I would expect that reports (especially the official ones) are reconfigured for TMP.

Atlassian should not recommend using an official report for TMP, that is based on fields only available in CMP. Thanks to awesome community leaders I was able to solve that with an automation workaround, but still, my report will be inaccurate for the next month or two, as suddenly I got 150 issues resolved in one day ;)

[Nic Brough -Adaptavist-]

I've got the configuration option in my JWM projects, so I'm not sure what you might be seeing.

But that bug report is absolutely right for others, the resolution field needs re-connecting.  Personally, I want the resolution field to go away as the determinant of "is it done", but that would break Jira Software for teams where "one person's done is another one's to-do", it's a massive reduction in flexibility.

You are completely right about the recommended reporting.  TMPs are not yet ready to be used, and you really should not have been forced into having to automate something.

[Trudy Claspill]

@Nic Brough -Adaptavist- 

Can you show us a screen image for the Configuration option being available in a JWM project?

[Nic Brough -Adaptavist-]

I am sorry, I have tried to explain that really badly.  JWM projects have configuration options, but they're horribly simple, often (but not always) called "project settings", and nothing like what other projects can do.

Try a JWM cloud new project, you'll see it.

[Trudy Claspill]

Ok, yes, there are some configuration options available in JWM project through Project Settings.

But, in JWM projects, there is no Columns/Status configuration page.

If you add another Status to the workflow, that automatically adds a column to the Board for that status.

If you add a column to the Board, that automatically adds a Status to the workflow to match the column name.

There is no option to modify the mappings of statuses to columns. There is only the option to change the order of the columns and that is done directly on the Board display rather than through any Project Settings or Configuration screen.

I think that's where we were getting confused. You seemed to be talking about the Column/Status mapping configuration as it exists in JSW, but that simply doesn't exist in JWM.