| Steps | Reference |
|---|
| From the main JIRA menu, select Projects , then choose Create with shared configuration (second item on the Create project dialogue footer menu); this shows the Create with shared configuration dialogue. | |
From the Choose a project dropdown list, select a project to use as a template for the new project. Press Next. | |
Next, the Create with shared configuration form appears; - Set your project Name and issue Key, and select the Project Lead from the user accounts (start typing and user name matches will appear as options for selection); the project Key has a maximum of 10 characters and must be alphabetic - numbers are not allowed (tip: use roman numerals for numbered projects, eg WRPSARII could be a key for project name WRP SAR II, WRPSARIV for project name WRP SAR IV etc)
- For MS projects the name should be <country code> <Release Date> Release i.e. "DK March 2017 Release". The Key should be <Country Code><Release ShortMonth><Year Code>, where the year code is 2016 = A, 2017 = B etc. i.e. DKMARB for a March 2017 release.
- Press Submit; this will create the project using the default schemes and show its Open issues view.
| |
| At this stage the project has been created with the relevant issue types, workflow, screen, permissions and notifications schemes, but is not yet visible to authoring applications. To do this, create the first issue as follows: | |
|---|
Use the Create button in the main JIRA menu to set up the first ticket in the project as the AP tracking ticket (also known as its "magic ticket")- Ensure Project is set to the new project name
- Ensure Issue Type is set to AP Authoring Project (select from the available issue types; make sure you don't select AP Authoring Task - they look very similar!)
- Press Next;
| |
The Create Issue screen will load ; complete any fields desired - As a minimum enter a Summary (typically this is set to the project name)
- If more details are available for the project, add these in the Description
- Optionally, set the Assignee to be the project lead (pick from the account name search selector - setting it may be useful for future status tracking, but it's not crucial - set this to Unassigned if the lead isn't agreed yet or you're unsure who it is)
- Optionally set the project category to AP (again, not crucial, but useful for filtering AP projects in JIRA)
- Enable or Disable AP Project Promotion Option (default is Enabled)
- Enable or Disable the AP Project MRCM Option (default is Enabled)
- For Managed Service Projects
- Enter Extension Base, this is the mainline branch for the project (e.g. MAIN/2016-01-31/SNOMEDCT-DK)
- Enter the Product Code to differentiate this from INT (e.g. DK, SE etc.)
- Press Create;
| |
- The newly created ticket as XXXXX-1 where XXXXX is the project prefix entered in the Create Project details; check that the ticket Type is AP Authoring Project
- NOTE: You need to create a task on the project to create the branch in the TS and then Classify and Validate the project before it can be used.
| |
