Request Type Summary Overwriting a JMWE Field Set Statement

[David B]

I am currently using JMWE to create a new request when an issue transitions to a status. In the create issue I set the Summary how I want it with some information from fields from the original issue etc. and when I test it out I noticed that the Summary I have for the request type of the new issue seems to overwrite what I want the summary to be. Has anyone ever run in to this before? I have done this before with other request types but this specific request type is just being a pain.

[Alex Koxaras _Relational_]

Hi @David B 

Usually JMWE runs after jira has run all their native functionalities and PFs. It could be:

• That you need to wait a few secs and refresh your screen. That summary change should be there
• You should search for another post function which overwrites your summary

In any case, chech the issue history to understand what's going on.

[Joseph Chung Yin]

@David B -

Using JMWE post function call for "Create Issue" action, you do have to specified the desired issue summary by default.  So if the newly created issues have a different summary value not your specified value, then you should look into your project's configuration - Especially if you have automation rules setup to ensure those rules are not overwriting your predefined value in JMWE.

Lastly, you should also look at your WF to ensure that no post-function at new issue creation time is adjusting the summary field value.  

Hope this also helps.

Best, Joseph Chung Yin