Jira Project Management Project Type

jira agile project types

Defining a project

This page tells you how to add a new project, configure an existing project or convert an existing project to another project type.

A JIRA project is a collection of issues. Your team could use a JIRA project to coordinate the development of a product, track a project, manage a help desk, and more, depending on your requirements. A JIRA project can also be configured and customized to suit the needs of you and your team.

On this page:

Before you begin
Creating a project
Convert a project type
Configuring a project
A note about project administrators

Before you begin

For all of the following procedures, you must be logged in as a user with the JIRA Administrators global permission. A JIRA administrator is able to create projects for all applications installed, but if the administrator does not have application access for that application, they will not be able to view the project after they have created it.

 

See More Different Types Of Science Fair Projects

Creating a project

Click Projects (in header) > Create project.
Follow the wizard to create the project.

About the project types:

Depending on which JIRA applications you have installed, you may have more than one project type available.
Each project type has a specific set of features.
All users on the JIRA instance will be able to see all projects, but what features they see and what actions they can take are determined by their application access and the project specific permissions.

About shared configurations:

When you create a new project from a template, that project is created with its own fresh set of schemes. These schemes are:
a permission scheme
a notification scheme
an issue security scheme
a workflow scheme
an issue type scheme
an issue type screen scheme
a field configuration scheme
Sometimes you may wish to share schemes among your projects, so that editing one scheme changes that scheme in several projects at once.
When you are creating a new project, select Create with shared configuration to select an existing project and to use that project’s schemes. Note that when you’re sharing schemes, any change to the scheme will affect all the projects using that scheme.

About the project details:

The project key will be used as the prefix of this project’s issue keys (e.g. ‘TEST-100’). Choose one that is descriptive and easy to type.
The project lead is a unique project role. Choose the person who manages the project as the project lead. If there is only one user in your JIRA system, the Project Lead will default to that person and this field will not be available.
If you’re creating a project using a project type related to an application you currently do not have access to, JIRA will display a checkbox that will allow you to grant yourself access to that application. This will add you to the default group of that application, and you will count as a user for that license.

See More Different Types Of Project Management Certifications

Convert a project type

At some point you may wish to convert an existing project to a different project type. For instance, you can convert a JIRA Software project to a JIRA Core project at the end of a JIRA Software evaluation period, or when your team grows. You can only convert to project types of JIRA applications that you have installed. Note that a project administrator may also change the project type.

Choose > Projects..

Locate the project that you’d like to change.
Select Change project type in the Operations column of the project you want to change.
Follow the wizard to change the project type. Only project types for applications you have installed will be available.

You can review more on project types and what your users will see on the project type and application overview page.
Configuring a project

Navigate to the administration page for the project by doing either of the following:


Choose > Projects. Select your project.

Navigate to the desired project’s summary and click the Administration tab.
Use the tabs on the left to navigate between the different project settings. Read the sections below for a description of each setting.

Project details | Issue types | Workflows | Screens | Fields | Settings | Roles | Versions | Components | Permissions | Notifications | Development tools

Project details

Click Edit Project at the top of the Project Summary page and edit the project details as desired. Note the following:

Editing the project key: This is not a simple task. Read this page before you edit the project key: Editing a project key.
Using the Wiki Style Renderer in the project description: You can use the Wiki Style Renderer to display rich text (HTML) in your project description.


Choosing a project avatar: If you don’t want to use a project avatar, you can upload a transparent pixel. This effectively loads the transparent pixel, which means you won’t see an image.

About project categories:

The project category is not edited in the Edit Project dialog. Instead, click the link next to the Category field (under the project name) on the project Administration page. Categories can be viewed/created via Administration > Projects > Project Categories.

Why are categories useful? JIRA can search for all the issues in a particular project category (e.g. category = “buildeng” in an advanced search), and can display projects sorted by the project category. A JIRA project can only belong to one category. Please note that a project category is not part of a project hierarchy. Also, JIRA does not support sub-projects or parent projects.
Issue types

JIRA enables you to keep track of different types of things — bugs, tasks, helpdesk tickets, etc — by using different issue types. You can also configure each issue type to act differently, e.g. to follow a different process flow or track different pieces of information.

Click either Issue Types in the left menu or one of the issue types under it, e.g. Bug, Task, Story, etc:

Issue Types: Click this to configure which issue types apply to this project (choose an issue type scheme or edit the existing scheme). You can also configure the workflow, fields and screens for the issue type in the project, but it is easier to do this by clicking one of the issue types.


One of the issue types (e.g. Bug, Task, Story): Click this to configure the workflow/screen for the issue type in the project. The workflow screen (Workflow tab) shows the workflow designer. The screen (View tab) shows the screen designer.

Workflows

Your JIRA issues can follow a process that mirrors your team’s practices. A workflow defines the sequence of steps (or statuses) that an issue will follow, e.g. Open, In Progress, Resolved. You can configure how issues will transition between statuses, e.g. who can transition them, under what conditions, and which screen will be displayed for each transition.

Workflow Scheme — the project’s workflow scheme determines which workflows (issue state transitions) apply to issue types in this project.

Screens

JIRA allows you to display particular pieces of issue information at particular times, by defining screens. A screen is simply a collection of fields. You can choose which screen to display when an issue is being created, viewed, edited, or transitioned through a particular step in a workflow.

Screen Scheme — the project’s screen scheme determines which screens are displayed for different issue operations (view, edit, create);
OR
Issue Type Screen Scheme — the project’s issue type screen scheme determines which screens are displayed for different issue operations (view, edit, create), for different issue types.

Fields

JIRA enables you to define field behavior: each field can be required/optional, rich text/plain text, hidden/visible. You define this behavior by using a field configuration.

Field Configuration Scheme — the project’s field configuration scheme determines which field configuration applies to issue types in this project. (A field configuration determines each field’s overall visibility, requiredness, formatting (wiki/rich-text or plain) and help-text).

Settings

Application Links (Configure project links) — if you have linked your JIRA instance to other Atlassian applications, like Confluence, FishEye or other JIRA instances, you will be able to link this JIRA project to areas of those applications that contain information relating to your project or team. For example, Confluence spaces, FishEye repositories, JIRA projects (in another JIRA instance), etc. This allows you to take advantage of integration points between these applications. See Using AppLinks to link to other applications for information about application links and project links.

Roles

Different people may play different roles in different projects — the same person may be a leader of one project but an observer of another project. JIRA enables you to allocate particular people to specific roles in your project.

Project Lead — user fulfilling the role of project leader. Used as the ‘Default Assignee’ (except for JIRA Software projects where it is set to ‘Unassigned’), and potentially elsewhere in JIRA (e.g. in permission schemes, notification schemes, issue security schemes and workflows).
Default Assignee — the user to whom issues in this project are initially assigned when created. Can be either the ‘Project Lead’ (above), or, if Allow unassigned issues is set to ‘On’ in JIRA’s general configuration, ‘Unassigned’. There are also default component assignees.
(info) By default, new projects also have their ‘Default Assignee’ set to ‘Unassigned.’ You can change this here if you want to set it to be a specific role, i.e. ‘Project Lead.’
Project Roles — members are users/groups who fulfil particular functions for this project. Project roles are used in permission schemes, notification schemes, issue security schemes and workflows.

Defines a project

This page idea you how to add new projects, existing projects or changes that are in place to other types of projects.

The Jira project is a collection of problems. Your team can use the JIRA project to coordinate product development, project lists, help desk and more depending on your needs. The JIRA project can also be configured and customized to suit your needs and your team.

On this page:

Before you start
Create a project
Convert type
Configure a project
A note about the project administrator

Before you start

For all the following procedures, you must be logged in as a user with the Jira Administrator’s global permissions. Administrators Jira can create apps for all installed apps, but if administrators do not have app access for the app, they will not be able to see the project after they’re compatible.

Create a project

Click the project (in the header)> Create project.
Follow the wizard to create.

About project type:

Depending on the JIRA application you have installed, you may have more than one type of project available.
Each type of project has a particular feature set.
All users in the JIRA example will be able to see all the projects, but what features they see and what actions they can perform according to their application.

About shared configuration:

When you create a new project from a template, the project is designed with its set of schemas. This scheme is:
Permission scheme
Schematic view
Security system problem
Workflow scheme
Schema type of problem
Screen system of issue type
Schematic field configuration
Sometimes you may want to share between your projects, so arrange one schema change system across multiple projects at once.
When you create a new project, select Create with a shared configuration to select an existing project and use the project’s schema. When you share the schema, any changes to the scheme will affect all projects using the schema.

About the project address:

The project key will be used as the key prefix for this project (e.g., ‘TEST-100’). Choose one that is descriptive and easy to type.
Prospect is a project. Choose who. If there is only one user on your JIRA system, the Project Leader will be the default person, and this field will not be available.
If you create a project using a project type associated with an application you currently do not access, JIRA will display a checkbox that lets you grant you access to that app. This will add you to the app’s default group, and you will be considered a user for the license.

Convert type

At some point, you may want to convert an existing project to a different kind of project. For example, you can turn a JIRA software project into. Inti Jira, at this moment. You can only convert the type of JIRA app application you have installed. Can also be done.

Select> Project ..
Find the project you want to change.
Select Change project type in the project column you want to change.
Follow the wizard to modify the type. Only the project type for the app you have installed will be available.

You can write more about the type of project and what your users will see on the project type and application overview page.
Configure a project

Navigate to the Administration page to do by doing one of the following:
Choose. Select your project
Scroll to the desired project summary and click the Administration tab.
Tab on the left to navigate between various settings. Read the sections below for a description of each setting.

Project details | Type of problem | Workflow | Screen | Field Settings | Role | Version | | Permissions | Notifications | Development tool
Project details

Click Edit Jobs at the top of the Summary page. Here’s what:

Editing project key: This is not a simple task. Read this page before you.
Using the Wiki Style Renderer in the project description: You can use the Wiki Style Renderer to display rich text (HTML) in your project description.
Choosing a projected avatar: If you do not want to use project avatars, you can upload transparent pixels. This effectively loads trans pan pixels
About project categories:

The project group is not edited in the Edit Project dialog. Instead, click the link next to the Category field (based on the project name) on the Project Administration page. Categories can be viewed/created through Administration> Projects> Project Categories.

Why are categories useful? Jira can search for all issues in a particular project category (e.g., category = “building” in advanced search), and can display projects sorted by project category. The Jira project can only fit into one category. Please note that the project type is not part of the project hierarchy. Also, JIRA does not support subprojects or parent projects.
Type of problem

JIRA lets you track different kinds of things – bugs, tasks, helpdesk tickets, etc. – by using various types of problems. You can also configure each type of issue to act differently, e.g. Follow different process streams or track different pieces of information.

Click one of the Problem Types in the left menu or one of the underlying issues, e.g. Bug, Duty, Story, etc.:

Kind of problem: Click this to configure the item type that applies to this project (select problem type schema or edit existing schema). You can also configure workflows, fields, and screens for the kind of issues in the project, but it’s easier to do so by clicking on one of these types of problems.
One type of problem (such as Bug, Task, Story): Click this to configure the workflow/screen for the kind of problem in the project. The workflow screen (Workflow tab) shows the workflow designer. The display (View tab) shows the screen designer.

Workflow

JIRA Issues You can follow a process that reflects your team practice. The workflow determines the order of steps (or statuses) that an issue will follow, e.g. Open, In Process, Complete. You can configure how the problem will switch between states, e.g. Who can transition them, under what conditions, and which screen will be shown for each change.

Workflow Scheme – the project workflow system determines the issue state transition applicable to publish the type in the project.

Screen

JIRA allows you to display a specific piece of problem information at a particular time, by specifying the screen. The screen is just a collection of fields. You can choose which screen to display when a problem is being created, viewed, edited, or redirected through a particular step in the workflow.

Screen Scheme – the project screen schema determines which screen is displayed for various troubleshooting operations (see, edit, create);
OR
Display Problem Type – Screen type project type schema determines which screen is shown for different operating problems (see, edit, create), for various kinds of issues.

Field

Jira allows you to define field behavior: each field can be requested / free, rich text / plain text, hidden / visible. You describe this behavior by using field configuration.

Field Configuration Scheme – the project field configuration scheme determines which field configuration applies to the issue type in the project. (The field configuration specifies overall visibility, suitability, format, wiki / rich-text or plain-text) in the overall field.

Settings

Application Link (Configure project link) – if you have connected your JIRA instance with other Atlassian applications, such as Confluence, FishEye or other JIRA examples, you can connect this JIRA project with the application area containing information related to your project. Or team. For example, the Confluence room, the FishEye repository, the JIRA project (in other Jira instances), etc. This lets you take advantage of integration points between these apps. See Using AppLinks to link to other apps for information about app links and project links.

Role

Different people may play different roles in various projects – the same person may be the leader of one project but another observer of the project. Jira lets you allocate certain people to specific roles in your project.

Project Lead – the user fulfills the role of project leader. Used as a ‘Default Specifier’ (except for the JIR Software project set to ‘Unassigned’), and potentially elsewhere in JIRA (e.g., in permission schemes, notification schemes, security systems and workflows).
The default recipient – the user who was the issue in this project, was initially assigned when it was created. Can be ‘Lead Project’ (above), or if Allow unspecified issues set to ‘Active’ in the general configuration of JIRA, ‘Not Assigned.’ There are also innate components built in.
(Info) By default, new projects also have ‘Default Assignee’ set
Version

Issues can be grouped in Jira by allocating them to the version. For example, if you use JIRA for product development or home building needs, you may want to specify your product or building (e.g., 1.0, 1.1, 1.2, 2.0, 2.0.1). Jira can help you organize, release and archive your version. The version may also have a Release Date, and will automatically be highlighted as “late” if this version has not been released at this time.

Which version. See the release management page for the edition.

Component

You may want several different parts to categorize and execute various problems. For software development projects, for example, you may have parts called “Database,” “Usefulness,” “Documentation” (see things that can belong to more than one component). You can choose the Default Setup for each element, which is useful if you have different people who have different sub-teams in your project.

These logical groups are the problem. See the component management page for editions.

Permission

You can also control who can access your project, and what they can do (e.g., “Work on Issues,” “Comment on Issues,” “Assign Issues”), using project permissions. You can also control access to individual items by using the security level. You can choose to grant access to specific users, groups, or roles (see the easiest tasks).

Permission Scheme – the project grant system determines who has the authorization to view or change the issues in the project.
Security Problem Scheme – Security Scheme Problems.

Notice

JIRA can tell the right people when certain events in your project (e.g. “Issue Created,” “Issue Resolved”). You can choose particular individuals or groups, or roles to receive email emails when events happen. (Read faster).

The Notice scheme – the open scheme to determine who receives email notifications about changes to problems in the project.

Email – specifies the ‘From’ address for emails sent from this project.Only available if the SMTP email server has been configured in JIRA.

(Warning) Please note, the Default Notification Scheme (sent with JIRA) with the outgoing mail server (SMTP) intended for emails to be sent immediately after an activity (example problem created) in this new project.
Development tool

This section is available only in the JIRA Software project and is only visible to users of the JIRA Software. This gives you an overview of connected development tools and which users can use the essential integration feature:

View permissions – on the display screen, as well as other development-related information, such as performing, engineering, and walking information. Msgr “See Development Tool.”
Applications – JIRA through application links and tools for JIRA development tools.

A note about the project administrator

An administrator in Jira is administrator permission, but not necessarily approval of Jira Administrator globally.

Without the authorization of Jira Global Administrator, the administrator can do the following:

Edit the project name
Edit project description
Edit avatar image
Edit the project URL
Edit
Edit role members
Change type
Define the component
Determine the version
View, but not selecting or writing schemes (image schemes, permission schemes, etc.)

Categories JATA. Jira Global Administrator.

Leave a Reply

Your email address will not be published. Required fields are marked *