No errors during bulk change of issues if use Filed Required Validator from JIRA Suite Utilities

Hello guys from JIRA Suite Utilities,

Issue and steps to reproduce:

1) Add Field Required validator to some Workflow transition

2) Bulk change one or more issue and do not enter anything to this required fields

3) Operation will be perfromed, BUT Transition will not be finished AND you will not get any warnings about the required field - So, no warnings and no changes to the issue - a bit strange behaviour)

 

Please confirm and advise if you could plan to fix it.

Many thanks!

1 answer

Hi Team, We are facing a similar issue with the plugin “JIRA Suite Utilities” installed. We can no longer clone an issue into a new JIRA issue. (Found the cause is the Validator in create issue transition “If a value for field Found Version/s is not provided during the transition, show the following error: Value in the 'Found Version/s' field is required..” We tried on 2 different issues whereby the base information is the same and we just need to change the problem description. Previously We would click More > Clone and then slightly change the heading (leaving the metadata the same like report version, module, etc.) and a new JIRA would be created, I would then modify the description and add new attachments. Currently a clone seems to insert a new link saying “Clones <current JIRA>” and “Is cloned by <current JIRA>” but no new JIRA tickets are created. Unable to render embedded object: File (image001.png) not found. In this example the clones links were deleted prior to hitting clone and then saving the new name does not modify the name. From Support team we tried cloning, no errors but found that attachments replicated. reopened issue and tried cloning, still same results, only attachments get cloned and no clone issue created. checked logs and found the following error [root@fclpjra03 log]# grep "RADIUS-17005" atlassian-jira.log 2014-10-27 13:06:12,646 http-bio-8443-exec-624 WARN girishsh 786x90302x6 17sgnhf 111.93.137.195,192.68.228.88 /browse/RADIUS-17005 [atlassian.plugin.webresource .DefaultResourceDependencyResolver] Cannot find web resource module for: com.atl assian.jira.jira-issue-nav-plugin:backbone 2014-10-27 13:06:43,703 http-bio-8443-exec-596 WARN girishsh 786x90582x1 17sgnhf 111.93.137.195,192.68.228.88 /browse/RADIUS-17005 [atlassian.plugin.webresource .DefaultResourceDependencyResolver] Cannot find web resource module for: com.atl assian.jira.jira-issue-nav-plugin:backbone 2014-10-27 13:07:35,800 http-bio-8443-exec-613 WARN girishsh 787x90875x2 17sgnhf 111.93.137.195,192.68.228.88 /browse/RADIUS-17005 [atlassian.plugin.webresource .DefaultResourceDependencyResolver] Cannot find web resource module for: com.atl assian.jira.jira-issue-nav-plugin:backbone 2014-10-27 13:08:27,048 http-bio-8443-exec-529 WARN girishsh 788x91169x2 17sgnhf

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,682 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you