Feature Requests

My team uses the date fields associated with Advanced Roadmaps to set the target start date and target end date on our Story tickets as part of our preliminary capacity planning for upcoming projects. The Issue Templating screen indicates that these custom date fields are not currently supported. KEY: { "schema": { "type": "date", "custom": "com.atlassian.jpo:jpo-custom-field-baseline-start", "customId": 11615 }, "fieldKey": "customfield_11615" } KEY: { "schema": { "type": "date", "custom": "com.atlassian.jpo:jpo-custom-field-baseline-end", "customId": 11616 }, "fieldKey": "customfield_11616" } These custom date field types should have the same level of support in the Issue Details form as datepicker field types.

We utilize the team field in Jira to organize our boards and easily view work by team on Jira Plans. It would be nice to have this option as a variable similar to the User Picker so we our users can auto-select this upon creation and easily set this ahead of time. Currently, we have to set the Team field after creation.

KEY: { "schema": { "type": "array", "items": "user", "custom": "com.atlassian.servicedesk:sd-request-participants", "customId": 10032 }, "fieldKey": "customfield_10032" } Note: Custom field id can be different in each instance

We are using issue templates for different issue types to make creating issues in our development project easier. But oftentimes people just click the "Create" Button in order to create an issue, and then the template isn't used. It's hard work to make everyone navigate to the templates overview first, then select the proper template. Ideally, people would click the "Create" button and then be offered the templates instead, starting with their starred templates.

It should be possible to duplicate a template to make minor adjustments without having to recreate the entire template from scratch

Presently, Issue Templates in Jira lack comprehensive support for all (custom) fields. Given the considerable effort needed to change this situation, along with existing technical constraints that prevent the support of certain fields entirely, we are actively seeking alternative approaches to address this challenge. Our goal is to find a solution that empowers users to resolve this issue independently, thereby enhancing Templating.app 's flexibility as a solution for Jira Templates.