Edit your project's workflows and screens

If your workflows or screens are only used by your project, you can now edit them to make sure they suit the way your team works. Go to workflows or screens to see how they're currently set up, and to make any changes you may want. Check out our documentation for more info, or talk to your Jira administrator.

Issue types

These issue types are available in your project. Each issue type can be configured differently.

Scheme: ASFJ: Scrum Issue Type Scheme

More

Workflows

A workflow is made up of statuses and transitions. An issue moves between statuses via a transition. The workflow defines what transitions and statuses an issue type can use.

Scheme: ASFJ: Software Simplified Workflow Scheme

More

Screens

A screen defines how fields are displayed for an issue. Different screens can be used when an issue is created, viewed, edited, or transitioned through a workflow.

Scheme: ASFJ: Scrum Issue Type Screen Scheme

  • ASFJ: Scrum Default Screen Scheme Default
  • ASFJ: Scrum Bug Screen Scheme
More

Fields

Fields hold the information about an issue, and each issue type can have different fields. How these fields behave is defined by a field configuration.

Scheme: System Default Field Configuration

  • Default Field Configuration Default
More

Priorities

Priorities define an issue's importance in relation to other issues.

Scheme:Default priority scheme

  • HighestHighest
  • HighHigh
  • MediumMedium
  • LowLow
  • LowestLowest

Settings

Some general project configuration options.

Versions

For software projects, Jira allows you to track different versions, e.g. 1.0, 2.0. Issues can be assigned to versions.

  • Release 1
More

Components

Projects can be broken down into components, e.g. "Database", "User Interface". Issues can then be categorised against different components.

This project does not use any components. Add a component

Roles

Jira enables you to allocate particular people to specific roles in your project. Roles are used when defining other settings, like notifications and permissions.

More

Permissions

Permissions define who can access a project, and what they can do within the project, and with the issues within that project.

Notifications

Notifications allow Jira to send email notifications to specified people regarding particular events in your project. They'll receive a separate notification for each event.

More

Development tools

Integrate your development tools with Jira to allow users to create branches right from their Jira issues and to provide visibility into commits, reviews, builds and deployments.

  • View permission:
    • Application access (Anyone on the web)
  • Applications:None