When I move issues from one project to an other, will each issues keep it statuses in workflow ?

[Romain Bonnecaze]

I'm currently moving issues from team managed project to company managed project. Will my issues keep their status in the current worklow to the new one if the workflows are identical from one projetc to an other ?

[Deleted user]

I was also looking for such a checklist. We have JIRA Software with Jira servicedesk.

Some things to test in UAT:

• Create queues in JIRA servicedesk
• find dashboards
• find kanban board, are all issues loading.
• count boards in db, before and after upgrade
• Can you still see attachments inside issues
• Do you have integrations, make test cases and see if they works
• Send incoming emails if configured
• Outgoing emails
• timereporting if Tempo is installed
• try different web browsers
• Check latest upgrade report
• find issues when searching
• create different JQLs to search for issues.
• Count the number of issues before and after upgrading (

  Issues - Search for issues (number or issues))

[Timothy]

1. Go through the instance check
   1. https://confluence.atlassian.com/support/instance-health-790796828.html
2. Make sure you get some of your users to UAT the instance before announcing the completion of the upgrade

[Angie Affolter]

I was actually looking for #2 - a list of things to review at the user level

Create an issue?  Open up a dashboard? search for issues?