I need to add additional statuses on my projects, but are unable to do so.

[Anneliese Pretorius]

From what I can find in other discussions, independently created projects will not allow you to add additional statuses.

I have a number of projects and would like to know if I can convert - and if so how, as well as how to create a project that is not deemed "independent"?

[Mark Segall]

Hi @Anneliese Pretorius and welcome to the community!

A couple quick notes to ensure we're aligned:

• Project Type: There are company managed and team managed projects.  Team Managed Projects allow you to create custom statuses as long as you have appropriate permissions.  Company Managed Projects require Jira Administrator permissions to make such changes
• Workflow vs Status: A workflow is a group of statuses that come together as a process.  Statuses are managed centrally in Jira settings

So with this added context, I want to make sure I understand what you're trying to accomplish.  Are you trying to:

• Add a new status to the system
• Add a new/existing status to an existing workflow
• Split out an existing workflow that is shared amongst projects and adding a new/existing status to the workflow

[Anneliese Pretorius]

@Mark Segall Thank you for the warm welcome!

I am working on Team Managed Projects, and have the required permissions.

I am trying to create new statuses to the system. I also attempted to create a new workflow containing these statuses, which I managed to assign to the different issue types, however, the statuses does not appear on the project dropdowns when trying to edit or create.

I can add using the board, but that implies that I have to go through each project and manually add each status one by one. 

Changing the Workflow is also a challenge which I have not mastered yet...

I would assume that, once I am able to change the workflow, the statuses associated with that workflow will automatically be updated as well?

[Mark Segall]

I can add using the board, but that implies that I have to go through each project and manually add each status one by one. 

Unfortunately, this is the very nature of a Team Managed Project.  They are purposely designed to empower individual teams with the ability to customize their projects without dependence upon a Jira Administrator. Each TMP as an isolated, sandboxed configuration.

So, as soon as you get into the realm of needing to employ governance and consistency across multiple teams, it's time to start thinking about migrating to Company Managed Projects that will offer the capability of shared configurations.

[Anneliese Pretorius]

Thank you Mark.

Can you perhaps provide a guide as to how to go about linking the workflow?

[Mark Segall]

Here's documentation for managing workflows in TMPs.

https://confluence.atlassian.com/jirasoftwarecloud/manage-how-work-flows-in-your-team-managed-project-1005805102.html

If you're interested in migrating from TMP to CMP, this will provide value:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

NOTE - The most important thing if you go this route is that any custom field data contained in a TMP will be lost.  The document simply says it needs to be recreated.  However, I typically take this approach:

1. Export my TMP project to csv - I typically extract these fields:
   • Issue Key
   • Summary
   • Created Date
   • Custom Fields
2. Create the new CMP
3. Bulk move all TMP issues to the new CMP
4. Update the csv from step 1 with the new issue keys
5. Perform an import mapping the TMP custom fields to their new CMP equivalent