Release Notes
Issue to Page for Jira - Version 2.1
published on 2020-06-19
The current version of Issue to Page (2.1) does not support the transfer of the post function via Botron SPI.
Bug
- Deactivated blueprints can be selected (Won't fix)
- JIRA keys are treated as a separate object in the insight name (Fixed)
Story
- The global or space-related templates can be called up and edited from the content configuration
- Existing page configuration and page content configuration can be copied and saved under a new name
- Epic information can be used in new variables
- Streamlined the "$project.key" variable so it can now be addressed as "$issue.project.key"
- User are be able to see an overview of the configured JQL in the page configuration
- UI Optimization
Issue to Page for Jira - Version 2.0
published: 2020-05-25
The current version of Issue to Page (2.0) does not support the transfer of the post function via Botron SPI.
Bug
- The templates are not sorted alphabetically (Fixed)
- The heading is not updated when changing between configurations (Fixed)
Story
- PagePrinter becomes Issue to Page
- Support for Botron SPI beta release, see restrictions here
- Can also address variables using the name of the custom field (Fixed)
- the documentation has been revised and extended
PagePrinter for Jira - Version 1.7.1
published: 2020-03-23
Bug
- Empty Profields values are not adopted (Fixed)
PagePrinter for Jira - Version 1.7
published: 2019-11-08
Bug
- Create Page is not displayed without JQL Filter (Won't Fix)
- No adoption of labels by PagePrinter (Cannot Reproduce)
Story
- Make PagePrinter variables available in the title, content and labels (Fixed)
Change request
- Date value as a variable in the page name (Fixed)