Skip to end of banner
Go to start of banner

JSU 2.1.0 Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

28th November 2017

JSU 2.1.0 brings huge improvements and refinements in many areas. Quite several of those had inspired by our customers. Because we like happy JSU users, the beecom team continues to make JSU even more powerful.


Change your scope: Connect your workflows not only of linked issues, but also of sub-tasks & issues in epic

Many JSU users love the new post functions Create Linked IssuesLinked Transition, which we introduced with JSU 2.0.0 .
Additionally to linked issues, you now can also create sub-task or issues in epics. Further Trigger a transition on any other issue, which is connected not only with an issue link, but also in a parent / sub-task, as well as epic / issue in epic relation.


Overcome permission obstaclesConnect your workflows of rather restricted projects

With Create Linked Issues & Linked Transition we did help you to bring teams of different JIRA projects closer together. However, the user still needed the appropriate permission in the project of the other team.
In JSU 2.1.0 you can configure a different user, who will create the new issue or trigger a transition on an existing one. Usually this will be a technical user with a lot of permissions, but no person logs into JIRA with it.

For example your support team has otherwise no permission in the developer's project. Now you can create a linked issue by using a technical user with the necessary permissions. And back the from the developers to the support, trigger a transition on the support issue with the technical user, whenever the developers task is done.

Also useful for complex business workflows with tight permissions. For example a customer of us, an international bank, has very restricted permissions for different projects due to legal constraints. In the past only a top manager was allowed to pass information from one project to the other, which he had to do all manually.
They are looking forward to JSU 2.1.0 which allows them for a fully integrated workflow solution over several projects, of which most employees cannot even see the other projects, which handle the process before or afterwards. 


Many refinements on 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: Copy a value from a connected issue (linked, sub/parent task, epic/issue in epic) to the issue in transition (triggering the post function). But also copy from the issue in transition to a connected issue.
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 1 post functions. Compared to the previous JSU, where you had to configure 1 post function for each field, your complex 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 'collecting' the values of its sub-tasks in one field of the parent task, whenever those sub-tasks get closed.


Put your validation error message in your context

Ok, we have to admit the standard validation error message, which JSU provided sometimes left the users rather puzzled.
What should they make out of a message like: "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,})$" ?
When actually what it means is: "Please provide a valid email address for Contact".

Now you can provide any massage, which makes sense for your users.


... and more

Small bug fixes, usability improvements, further details in the documentation.





JSU 2.1.0 Release Notes

November, 28th 2017


JSU 2.1.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 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 obstaclesConnect 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 trigger a transition on an existing one. The user 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 JSU 2.1.0 they can now construct a fully integrated workflow solution over several projects, where most employees cannot even see other projects, which handle the processes before or after their work.

 

Many refinements on 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:

  • Copy a value from a connected issue (linked, Parent/Sub-Task, Epic/Issue in Epic) to the issue in transition (triggering the post function).
  • Copy from the Issue in transition to a related Issue.
    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 massage, which provides actual information for your users.

 

... and more

Small bug fixes, usability improvements, further details in the documentation.

 


  • No labels