The Workflow option does'nt appear in the project settings in Jira.
Asked by Gabriel Vieira:

Hello, everyone!

The Workflow optiont does'nt appear in the project settings in Jira.

I have an administrator account, but I can't find the option to add a workflow to standardize my Jira projects. And i have a free product plan.  
![Captura de tela 2024-09-03 140725.png](https://community.atlassian.com/t5/image/serverpage/image-id/345336iE415C16C618A3031/image-size/large?v=v2&px=999 "Captura de tela 2024-09-03 140725.png")


Answers:
author: Samuel Gatica
body: Hi [@Gabriel Vieira](/t5/user/viewprofilepage/user-id/5583322)

Welcome to the community!

The project type you may be utilizing for that is Team-Management, hence the workflow options should be listed in the Issue Types instead.

Please refer to the articles:

* [Set up a workflow in a team-managed software project](https://support.atlassian.com/jira-software-cloud/docs/set-up-a-workflow-in-a-team-managed-software-project/)
* [How to create workflows for team-managed projects?](https://support.atlassian.com/jira-work-management/docs/how-to-create-workflows-for-team-managed-projects/)
* [Manage how work flows in your team-managed project](https://support.atlassian.com/jira-software-cloud/docs/manage-how-work-flows-in-your-team-managed-project/)

Best regards

Sam

comments: author: Gabriel Vieira
body: Hello, [@Samuel Gatica](/t5/user/viewprofilepage/user-id/753028) !

Thanks for your help.

So i cant standardize my workflow projects?

If I have developed a dashboard, and use the status parameters of the projects, will I have duplicate parameters due to the non-standardization of workflows? Even editing them one by one?

Like This:

![Captura de tela 2024-09-03 142303.png](https://community.atlassian.com/t5/image/serverpage/image-id/345344i30F3CEEC061804E4/image-size/large?v=v2&px=999 "Captura de tela 2024-09-03 142303.png")


author: Samuel Gatica
body: Hi [@Gabriel Vieira](/t5/user/viewprofilepage/user-id/5583322)

To standardize the workflow, it is recommended to utilize a company-managed project. This approach allows for the sharing of workflows across all issue types, thus preventing the creation of duplicate statuses.

However, please note that transitioning from a team-managed project to a company-managed project is not a straightforward process. It requires the manual recreation of all issue types, workflows, and custom fields, followed by migrating all existing issues to the newly created project.

For more detailed guidance, please refer to the following link: [Migrate between team-managed and company-managed projects](https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/)

***Things to keep in mind if you migrate from team-managed to company-managed***   
Team-managed projects and company-managed projects are technically quite different. Here's a few things to consider when you migrate from a team-managed software project to a company-managed software project:

* Board statuses: If you customized your team-managed board, you'll need to set up the same statuses in your company-managed project's workflow. Only Jira admins can create and modify statuses and workflows. Learn more.
* Custom fields: If you use custom fields in your team-managed project, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed project. Custom field data will need to be recreated, otherwise it will be lost.
* Issue types: If you added your own issue types to your team-managed project, you'll need to have a Jira admin recreate these using an issue type scheme that they associate to your new company-managed project. Learn more.
* Project access: Access to company-managed projects is controlled by a permissions scheme. Only your Jira admin can update your company-managed project's permission scheme. Learn more.
* Project and issue keys: Jira will automatically update the issue keys of migrated issues to reflect their new project. Any existing links to old issue keys will be automatically redirected.
* Reports: Reports data won't be saved. Even though your issues will be retained, data for your project's Velocity and Burnup reports won't transfer over, and will be lost.
* Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in company-managed projects (Story points) is different to the custom field used in team-managed projects (Story point estimate).

Hope this helps!

Best regards

Sam


Tags: cloud

jira-cloud