Business project reports

[time design]

Hi! I'm managing a Business Project, of the Team-managed business type with Jira Work Management. We chose this type of project due to the large amount of reports available, however I cannot use them.

When trying to consult the performance charts, they all take into account the "solved" status, while the board only contains the "done" status. I've read several articles in the community, but the status update options for resolved or a custom filter in the reports is not visible. How should I proceed?

Another point is the priority display in the kanban for Business project, despite the option being activated in the customization of cards, the option is still not displayed.

[Tarun Sapra · Accepted solution]

Hi, You should click on retaining reporters and assignee otherwise you would loose them, this happens if the new field configuration scheme has reporter required and the old reporter no longer has permission to be the reporter anymore.

To be honest, I don't like the whole IssueType migration process, I have lost some data on production becasue of the poor user experience and had to sync with backup using a script, i also reported the matter of poor UX to Atlassian and they created this ticket -

https://jira.atlassian.com/browse/JRA-36801

[Alex Perez]

Hi!

In all my attempts I have used the "retain" option, but the migration assistant doesn't allow me to continue to the next screen because "reporter is mandatory".

Please note that there are no changes in permission scheme (users that could be assigned or report issues will remain having this permission) nor in the field configuration scheme (reporter/assigned is a required field before and after config migration).

Any clue why jira is asking me to overwrite reporter and assignee when changing issue type scheme?

[Alex Perez]

Hi again :)

Just made a copy of the Field configuration scheme, and changed the reporter/assignee to optional. Then applied this scheme to the project.

Now the Issue Type scheme migration assistant lets me change the scheme, retaining reporter/assignee. Once the migration is completed, I could change the Field configuration scheme back to the original.

I don't understand the relationship between issuetype scheme changes and field configuration screen config :?

[Tarun Sapra]

When you change the IssueType Scheme, the new issuesTypes are validated against the field configuration, so if the reporter if mandatory in the field condiguraiton that results in migration failing as the validation of the issueType with field configuration enforces the reporter to be present even on older issues which might not have a reporter.

[Alex Perez]

At this point, I think that I'm hitting these bugs:

https://jira.atlassian.com/browse/JRA-16476

https://jira.atlassian.com/browse/JRA-16441

If I'm trying to change only the IssueTypeScheme, and the permission scheme remains the same in the project .. why Jira migration wizard is asking me what to do with original reporter and assignee?