Skip to main content
Skip table of contents

Release Notes 17.2.0

New Features:

🔥 Ability to create a Template without an existing Jira Issue

Now you can create a Template in such a way:

  • create Template from scratch - Build a new, custom template starting with no predefined content or structure

  • Create Template from existing issue - Use a pre-existing Jira issue as the basis to create a new template

  • create Template from Hierarchy Node - Use a specific hierarchy node within as the foundation for a new template

How to create Template: Create Template

🎯 API

In this release, we have introduced an exciting new feature - the addition of an Application Programming Interface (API) to SITC. This API empowers users with enhanced functionality, enabling them to perform key actions such as applying templates, applying hierarchies, and creating/editing schedulers programmatically. This integration opens up opportunities for automation and seamless integration with other systems or processes.

How to enable the API function for SITC: SITC API

With API you can automate your process for Applying the Templates and Hierarchies, Creating and Editing the Schedulers for the Hierarchy. For this, you can use Jira Automation or Postman.

To create a rule for Jira Automation: API configuration | To create a rule for Jira Automation:

(tick) Simple and Advanced Modes for Applying Templates

For applying the Template we added two modes:

  1. Apply without adding changes to the issue - the ‘Create’ button in the ‘Apply Template’ dialog

  2. Apply Issue by adding changes to the Issue fields - the ‘Advanced Issue Creation’ button in the ‘Apply Template’ dialog

    image-20240125-105909.png

Read more about applying modes for the Templates: Apply Template | Applying-Modes-for-the-Templates

🎯 Post function for Applying Template

The ‘Post' function is a new addition to the existing 'Apply Template’ feature. Using the Post Function you can automate the process of applying the Templates

How to use Post Function: SITC Post function for Applying Template

🎯 Support for the current user name in the Assignee and Reporter fields while Importing the Templates from the Server

For imported Templates from the Smart Issue Templates for Server, we added support for the current user name in the Assignee and Reporter fields

image-20240126-201731.png

How to use the Import Templates function from Server to Cloud: Import Templates to Cloud

🎯 Support for the ‘Parent’ field for the Templates and Hierarchies

Now we support the Parent field for the Template and Hierarchies.

Fill in the Parent field while creating or editing Hierarchies, Templates

The Parent field is available only for the Premium Jira subscription

xC6fyXOS7X.png

⬆️ ‘Permissions’ section on the Getting Started page

To Getting Started added section ‘Permissions’. Where you can what Jira permissions and SITC Permissions you need to have for some actions.

image-20240127-130559.png


Bugs fixed:

  • The "Favorite" icon near the folder's name on the "Manage Hierarchies" and the " Manage Templates" pages go out of bounds when the folder's name is too long

  • The user icon is not changed for the ‘Reporter’ field on the ‘Create/Edit Hierarchy’ page after the user changed his own avatar in the Atlassian account settings and added the Node from Template

  • The error message ‘There was an error invoking the function - Cannot read property 'system' of undefined’ is shown on the Manage Templates page after creating the Template from Hierarchy Node

  • The ‘Issue type’ field wasn`t cleaned in the ‘Import Template’ dialog after changing the Project during Importing the Template

  • The template created from the Hierarchy Node is broken if the Hierarchy Node has a custom issue type

  • The created Hierarchy is not shown in the Hierarchy list on the Manage Hierarchies page after sorting Hierarchies by created date

  • Cannot create a Template on the Manage Templates page when choosing a way to create a template with Hierarchy Node AND from the Existing issue

  • Cannot create a template on the Manage templates page when choosing a way of creating a template with Hierarchy Node

  • The Jira issue page is not open after applying the Template and clicking on the Issue key

  • The ‘Template Content’ field is not shown on the Edit Template dialog of Template was created from the Hierarchy Node

  • The ‘You've created undefined issue.’ notification is shown on the Manage Templates page after applying the Template created from scratch

  • The Template is not applied if the Templates was created from the Hierarchy Node with used Hierarchy Variables

  • The empty page appears on the Manage templates page (Edit template dialog) when clicking on the Template content button for Template created from Node with User and Text variables

  • The variable values are not applied to the Jira Issue after applying the Template with user variables in the fields

  • The blank page is shown on the Manage Template page after clicking on the ‘Template Content’ button for the newly created Template from Hierarchy Node

  • The ‘Parent’ field is not shown in the Node dialog on the Create Hierarchy page

  • The way of creating a template changes to "Template from existing issue" on the Edit Template dialog when a template was created From Scratch or from Hierarchy Node, and updated after that

  • Cannot add Node from a template on the Create Hierarchy page when a template was created from Scratch AND from Hierarchy Node

  • The blank page appears on the Manage templates page when opening this page

  • All Transition types are highlighted in the list after selecting one Transition type from the list

  • Only the ‘All’ Hierarchy folder is shown on the Manage Hierarchies page when opening the Manage Hierarchies page

  • The ‘star’ icon for Favorite Template is grey in the Template list on the Apply Template dialog

  • The value for the ‘Parent’ field is not applied to the Jira Issue after applying the Template

  • Cannot create a template on the Manage Templates page when creating it with the "Set preinstalled" function

  • The checklist cannot be applied with the Template on the Jira Issue view dialog when the template was created with each of the three available ways

  • The search is not working in the ‘Parent’ field for Templates and Hierarchies after entering the special symbols

  • Node numbers are not getting updated after a deletion. (Deleted Node number is permanently not found)

  • The value for the Assignee and People fields are empty in the Jira Issue after applying the Template created from Hierarchy Node where the user variable was used in the Assignee field

  • The value for the custom fields are not applied to the Jira Issue

  • The ‘Apply Template to issue’ function is broken after trying to apply the Templates created from the Hierarchy Node

  • The blank page is shown on the Manage Templates page after clicking the ‘cross’ icon for the project in the ‘Apply Template’ dialog

  • The Template is not applied if was used ‘labels’ and 'dropdown', and the Template was created from scratch and from the Hierarchy Node

  • The blank page is shown on the Manage Templates page after clicking on the ‘Show empty optional fields’ option

  • The blank page appears on the Create Hierarchy page when updating the Hierarchy (which has 2 more custom fields filled in) by adding fields like "Checkbox" and "People"

  • The Template is not APplied if was shared permissions for applying with another user

  • Only one checklist is applied to the Jira Issue after applying the Template from the simple mode of applying

  • The ‘Deleted user’ value is shown in the Reporter/Assignee fields for the User Hierarchy variable instead of the name of the variable

  • The error ‘Cannot read properties of undefined (reading 'find')’ is shown in the console after adding several Hierarchy Node at one time and selecting project and issue type for one of them

  • Cannot apply a template on the Manage templates page when a template was created "from scratch" or "from Node" and contains "People" field

  • The Template is not applied to another company-management project on the Manage Templates page if the Templates was created from scratch and used value from the ‘Components’ field

  • The sub-task issue type is shown on the Create Template dialog while creating a Template

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.