Projects are defined above the scope of the query engine:
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.
Projects can be converted on a case-by-case basis:
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, and select the relevant project..
Select Details in the Project settings menu.
Change the project type, and click Save details. Only project types for applications you have installed will be available.
Jira is expecting me to specify the project type on the import configuration file, but I don't know which name to use.
- Business type is for non-software projects, and does not include Agile boards
- Software type is for software projects, and includes Agile boards
The minimum information for a CSV import is:
IssueType, Summary, Project Name, Project Key
bug, "First issue", Sample, SAMP
bug, "Second issue", Sample, SAMP
task, "Third issue", Example, EXAM
The project key is the prefix for all issue IDs in your JIRA project.
To avoid project type in a JQL query, use one of the following:
Find issues in projects that are led by a specific user:
projectsLeadByUser(username)
Find issues in components that are led by a specific user:
componentsLeadByUser(username)
Perform searches based on issues that are linked to a specified issue:
linkedIssues(issueID)
References