Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
JSU 2.2.0 Release Notes
February, 1st 2018
JSU 2.2.0 introduces great improvements and various feature enhancements. With this release we tackle real world requirements of our customers – to scale the users’ benefits and provide more powerful solutions.
Change your scope: Connect workflows – and this is new - of Sub-Tasks & Issues in Epic
The powerful combination of “Create Linked Issue” and “Linked Transition” is well-liked in teams to automate their processes. With version to features we introduces in JSU 2.1.0 you are now able to not only create linked Issues, but also Sub-Tasks and Issues in Epics. This comes along with the possibility to trigger a transition on any relating Issue i.e. Issues in Parent/Sub-Tasks and Epic/Issue in Epic relation.
Deal with permission obstacles: Connect workflows of restricted projects
Even though JSU 2.0’s “Create Linked Issues” & “Linked Transition” allows to bring teams and the work of different Jira Projects closer together, you might face permission difficulties. The user still needed the appropriate permission in the project of the other team.
In JSU 2.1.0 the new “…as User” feature allows to configure an intermediate user, which creates the new Issue or triggers a transition on an existing one. This user account is assumed to be only technical, with broad permissions, but not used to log into Jira by in life persons.
Imagine your support team has no permissions in the developer’s project and vice versa.
You can now use this technical user (with the necessary permissions) to create a linked Issue in the developers project – and to trigger a transition on the support task out of the developers project, when done.
A real life problem we wanted to address:
Due to legal constraints an international bank has very narrow permissions for all kind of different projects. Only a top manager was allowed to manually pass information from one to the other project. With andvarious enhancements to existing functionalities.
Scope, Scope, Scope...
We introduced Scopes in JSU 2.1.0 they can now construct a fully integrated workflow solution over several projects, where most employees cannot even see the other projects, which handle the processes before or after their work.
Many refinements on to several Post-Function like "Create Linked Issue" or "Copy Value From Other Field
We went even further and introduced the new concept of different Scopes to the “Copy Value From Other Field” post function.
Both is possible:
". We extended the same feature to "Update Issue Custom Field". Your are no longer restricted to updated a Custom Field inside the same issue. You can now update any liked issue either through 'Issue Linking', Parent/Sub-Task
, Epic/Issue in Epic) to the issue in transition (triggering the post function).For example you could copy the Due Date from an Epic to a Story, whenever you Start Progress on the Story.
You can now copy any number of fields during a single post function. Compared to the previous versions, where you had to configure one post function for each field, your confusing workflow configurations get much cleaner now.
Additional options to append or prepend the copied value to any existing value.
Imagine a Parent task which is ‘gathering’ the values of its Sub-Tasks in one field, whenever those Sub-Tasks get closed.
Put validation error messages in your context
We admit that the standard validation error message, which JSU provided was rather cluttering.What should you make out of: "The field Contact its contents must match against the regular expression ^[_A-Za-z0-9-\\+]+(\\.[_A-Za-z0-9-]+)*@[A-Za-z0-9-]+(\\.[A-Za-z0-9]+)*(\\.[A-Za-z]{2,})$" ?
Even if it just means: "Please provide a valid email address for Contact".
Now you can implement any message, which provides actual information for your users.
... or Epic.
'Issue Linking': We went even further and introduced the value ANY for 'Issue Link' definition. You have now the full flexibility to update a field or copy a value to ANY 'Linked Issues'.
... and more
Small bug fixes , and usability improvements, further details in the documentationand stability improvements.