image
See how Jira + Innovalog can help
4 minutes reading time (724 words)
Featured 

New features in JMWE for Jira Server 6.1

whats-new-in-jmwe-6-1

We are excited to announce several new features, plus many improvements, that will give Jira Admins considerably more options in configuring their workflows. Here is what's new in Jira Misc Workflow Extensions (JMWE) for Jira Server:

1. SET STATUS FIELD

The Status field can now be set directly in most post-functions, including Create/Clone Issue(s) and Set Field Value. 

In the Create/Clone Issue(s) post-function, for example, this means that during the creation of a new issue, the workflow can start at a Status different from its initial Status. 

First, add the Status field to the post-function. Then, you can set to copy the value from the current issue, or set the field value to a constant or Groovy template, or Groovy Expression.

It's important to know that changing the Status field value directly (as explained above) will not validate potentially required fields, such as the Resolution field. It will also leave no trace in the issue history. Therefore, this option should be used only in specific cases. We recommend you to refer to our documentation page when configuring this option.


2. CHANGE ISSUE TYPE FIELD

The Issue Type field can now be changed, and the workflow of the issue will be adjusted accordingly.

Thanks to workflow schemes, when you change the Issue Type field in post-function configuration, the associated workflow will now change accordingly. 

Keep in mind that changing the issue type should only be done if:

  1. the current and new issue types share the same workflow (using workflow schemes)
    OR
  2. the issue's Status exists in both the current and new workflow​.

3. "ANY" LINK TYPE

In extensions that operate on linked issues, such as the Transition Linked Issues post-function, you can now specify "any" as the link type.

It allows for much greater configuration flexibility as in addition to selecting the link from the Issue Link drop-down, you can now leave it as Any for any link type other than Issue/Subtask, Epic/Story and Jira Portfolio hierarchy.

It is supported in the following post-functions:

  • Clear Field Value of Linked Issues
  • Copy field value to linked issues
  • Copy field value from linked issues
  • Set field value of linked issues
  • Transition linked issues
  • Comment linked issues


It is also supported in the Linked Issue Status Condition and the Linked Issue Status Validator.
 


4. COPYING TO DIFFERENT FIELD

When copying a field to or from the linked issues or the parent issue, you can now specify a different field to copy to.

The Copy field value from linked issues, Copy field value to linked issues, Copy field value from parent issue and Copy field value to parent issue post-functions now also allow copying to a different field than the source field (for example, from Reporter to Watchers).

5. COPYING ISSUE LINKS

You can now copy issue links between issues.

In the Create/Clone Issue post-function and the Copy to/from Linked/Parent Issues post-functions, you can now copy issue links between issues. For example, you might want to take advantage of it when creating a bug in Project B if the developer confirms a Bug in Project A.

6. MLCS CUSTOM FIELD SUPPORT

The Multi-Level Cascading Select app is now supported. 

If you have this 3-rd party app installed, you are now able to set the Multi-Level Cascading Select (MLCS) field directly when creating an issue via a post function. Just add the #MLCS field in "Set fields of new issue" and specify the value.

 There are other new features - read the JMWE 6.1 release notes.


PLUS...

We've heard your feedback and made some improvements to our current functionality. Check them out:

BETTER COPYING

Copying comments between issues now adds a new comment without delete existing comments. It also avoids duplicating comments that were already copied before. Copying the attachments field -- adding new values -- now only copies new attachments.

BETTER FIELD PICKER

Post-functions, conditions, and validators that require selecting fields now use a searchable field picker instead of a simple dropdown menu.

BETTER ERROR HANDLING

There is a new option in the JMWE global configuration page to set how post-function errors are handled: you can now select whether to display errors for all, admins only, or no one. By default, errors will be displayed for admins only.

1
We are looking for Java and Full Stack Software En...

Related Posts

 

Comments

No comments made yet. Be the first to submit a comment
Guest
Friday, 20 September 2019

Captcha Image