Defining schemes in a create project template add-on

[Thomas Hardin]

Hello all,

I am in the process of creating project templates using the [Create a Project Template | https://developer.atlassian.com/server/jira/platform/creating-a-project-template/] guides. I've been fairly successful with the existing configuration json as I can add/change workflows within it, however; I am trying to expand this so that I can add screen schemes and if possible all other schemes. After researching, I found a developers post where an example json was posted (https://community.developer.atlassian.com/t/how-to-define-screens-in-project-template/5732). I altered it to support what I was using, but once I compiled and deployed the add-on, I received an error when I tried to create a new project.

Here is a copy of the json I am using:

{
 "issue-type-scheme":
 {
 "name": "Task Tracking Issue Type Scheme",
 "description": "A collection of Issue Types for tracking projects and tasks.",
 "default-issue-type": "taskType",
 "issue-types": [
 {
 "key": "epicType",
 "name": "Epic",
 "description": "A big user story that needs to be broken down.",
 "icon": "/images/ILEAD-Develop-negative_small.png",
 "screen-scheme":"epicDefaultScreenScheme"
 },
 {
 "key": "taskType",
 "name": "Task",
 "description": "A task that needs to be done.",
 "icon": "/images/ILEAD-Develop-negative_small.png"
 },
 {
 "key": "subtaskType",
 "name": "Sub-Task",
 "description": "A sub-task of the issue.",
 "icon": "/images/ILEAD-Develop-negative_small.png",
 "screen-scheme":"subtaskDefaultScreenScheme",
 "sub-task": true,
 "workflow": "simpleWorkflow"
 }
 ]
 },
 "workflow-scheme":
 {
 "name": "Standard Task Workflow Scheme",
 "description": "A collection of Workflows assigned to Issue Types, used in projects for tracking projects and tasks.",
 "default-workflow": "taskWorkflow",
 "workflows": [
 {
 "key": "taskWorkflow",
 "name": "Standard Task Workflow",
 "description": "Basic 3-step workflow for JIRA new project creation blueprint.",
 "workflow-bundle": "/workflows/Issue-Tracking-Workflow.jwb"
 },
 {
 "key": "simpleWorkflow",
 "name": "Standard Simple Workflow",
 "description": "Basic 2-step workflow for JIRA new project creation blueprint.",
 "workflow-bundle": "/workflows/Software-Simplified-Workflow-for-Project-TTP.jwb"
 }
 ]
 },
 "issue-type-screen-scheme":
 {
 "name": "Task Tracking Issue Type Screen Scheme",
 "description": "A collection of tabs and fields, used for tracking Tasks and Projects.",
 "default-screen-scheme": "taskDefaultScreenScheme",
 "screens": [
 {
 "key": "taskDefaultScreen",
 "name": "Task Tracking Default Screen",
 "tabs": [
 {
 "name": "Field Tab",
 "fields":[
 "issuetype",
 "summary",
 "description",
 "attachment",
 "priority",
 "duedate",
 "reporter",
 "assignee",
 "labels"
 ]
 }
 ]
 }
 ],
 "screen-schemes": [
 {
 "key": "taskDefaultScreenScheme",
 "name": "Task Tracking Default Screen Scheme",
 "default-screen": "taskDefaultScreen"
 }
 ]
 }
}

I haven't changed anything else with the add-on, but I know that others have added additional coding in the  project hook.java, which may be what I need. I don't know.

If anyone has some suggestions, I would be grateful. At the end of the day, I want to be able to re-use this for our company as they are implementing some new standards, all of which, rely on Jira.