Do I need a Workflow scheme, an issues scheme, and a screen scheme for my one project?

[Jean Ann Harrison]

Hi all;

I've been trying to learn how to configure my project which will be used by my small team of less than 10 people right now.  I do have Jira Admin rights and trying to figure out if these complicated schemes and screens are necessary.   My project workflow I is one which takes an epic, story, task and bug through our lifecycle  of "to do", "in process", "Code Review", "Ready for Test", "In Test" and "Done" with some statuses added like "Failed" and "Won't Fix".  However, each status do not need various screen types but I would like my Kanban board to reflect these statuses however, I can't seem to display these statuses on my Kanban board.  

Any advice as to what I should be setting up?  

I do know how to associate a workflow scheme to my workflow.  I know how to publish my workflow.  I've tried these and yet I don't see this workflow reflected on my Kanban board.  

When I go to manually change my board settings, I see the message "unmapped statuses but not sure what I should be doing to map them.  Screenshot below:

What else do you need to know?

[John Funk · Accepted solution]

Hi Jean Ann,

The quick answer is yes, you need all of those schemes. 

For the workflow and statuses question, you simply drag the status from the unmapped statuses area to one of the columns. That way any issues currently in that status will show on the board. 

[Jean Ann Harrison]

Thank you kindly for your answer @John Funk

I'll keep working on my project to get it right.  

[John Funk]

You are very welcome. 

[Trudy Claspill · Accepted solution]

Hello @Jean Ann Harrison 

When you add Statuses to your workflow, you need to also add those statuses to Columns displayed in your board.

You can either drag those statuses from the Unmapped area and drop them under the status in one of the existing columns (To Do, In Progress, Done), or you can click on the Add Column button to add new columns with different names and move the unmapped statuses to the new columns.

The issues that are set to those Status values will display in the Columns to which you map the Statuses. You can have multiple Status values mapped to one Column, or you can have a separate column for each Status.

If you have created a Company Managed project then you will have gotten defaults for all the Schemes you mentioned. Yes, you must have those Schemes. You can continue to work with the defaults, or as a Jira Administrator you can modify them.

Alternately you can create a Team Managed project. Team Managed projects do not use Schemes. They are intended to be stand-alone projects that can have their own customizations independently from customizations in any other Team or Company Managed project. Customizations for Team Managed projects can be made by the users assigned to the Administrator role in that project. You may find that type of architecture easier to manage since it does not involve all the Scheme management of Company Managed projects. You can learn more about how Team Managed and Company Managed projects differ through the documentation here:

https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/

Or through the Atlassian University course on managing projects in Jira Cloud here:

https://university.atlassian.com/student/page/840992-acp-620-managing-jira-cloud-projects-certification?sid=4d5fc6f8-1fbb-4f13-b2aa-2cb9fcce9eff&sid_i=0

[Jean Ann Harrison]

@Trudy Claspill  Once again Trudy, you helped me out so much.  I've created a company managed project because I will need to create customized fields for my team to be able to utilize.    I'll keep you posted as to how I get along.   I've been studying much documentation but I felt there was no real sequence of what should be done when regarding starting a brand new project.  I'll keep trying.    Many thanks for your patience.