Rainbow hinders Status change JIRA Issue when Git commit and Crucible is used


1. Enabled add-on Rainbow

  • install and configure Add-on Rainbow

  • commit via Git and Crucible

  • JIRA issue Status does not do the Transition, still Open

2. Disabled add-on Rainbow

  • disable Add-on Rainbow

  • commit via Git and Crucible

  • JIRA issue Status does execute the Transition and is Fixed

3. Enabled add-on Rainbow

  • enable Add-on Rainbow

  • commit via Git and Crucible

  • JIRA issue Status does not do the Transition, still Open
    We have also tried with changed Select Criteria from Status to Resolution, does not allow changed Status either.

Additional info:

hints: we use these Calculated Number fields to support easy and quick select Issues with most number of issues from other support systems related to JIRA issues.
Although, these fields are not available for CR Issue Type which should be triggered with this Git commit...


JIRA Server, Version 7.0.10 Build Number 70120
Crucible Version
FishEye 3.10.2 20151130101412
Crucible 3.10.2 20151130101412


Hubert Gabel
March 14, 2016, 10:17 AM


We installed 1.0.2. but apparently got the same results as the earlier

Which of the logs we can create from JIRA is most helpful to you?
Create Support Zip

This tool will allow you to create a zip file containing useful information
about your instance. No information will be sent to Atlassian.
Application Properties
Memory statistics, configuration options, and other key information. (required)

Thread Dumps
Generate and include a Thread Dumps (3 thread dumps 5 seconds apart).

JIRA Configuration Files
Your database settings and other useful information. (recommended)
Tomcat Configuration Files
Tomcat configuration files such as server.xml and web.xml.
Healthchecks Results
The results of Healthchecks in your instance. (highly recommended)
Authentication Configuration Files
Authentication configuration files such as atlassian-user.xml, osuser.xml
and crowd.properties. Atlassian will handle your data with strict
confidence and will not disclose it to any third parties. NOTE: Usernames,
etc. referenced in your log files are NOT anonymised. (recommended)
Cache Configuration Files
Cache configuration files, which are useful in diagnosing performance
JIRA Application Logs
Your JIRA application logs. (highly recommended)
Tomcat Logs
Tomcat log files, e.g. catalina.out. (recommended)
Limit File Sizes?
Limit the size of files included in your support zip to no more than 25Mb.

Deniz Oğuz
March 14, 2016, 10:41 AM

thanks for the information. I will install exact fisheye version and jira integration and try it.

Deniz Oğuz
March 15, 2016, 9:20 AM


Although I still could not reproduce the error, I'm fairly confident this version solves your issue. Somehow Rainbow field is seen as a Text field. Issue does not happen for me even with 1.0.1 version. Hopefully Atlassian gives JIRA's source code to its customers and I have traced from their source to find the error. I really appreciate it if you could give it a quick try, after that I will publish it to marketplace. Please uninstall the previous version before installing the new one. Thanks for your effort to solve the issue.

Hubert Gabel
March 15, 2016, 10:42 AM

Hi Deniz, installed

, committed from within Git, saw change in Crucible and the expected Status change in JIRA. Issue solved.
What we also notice however, if 'Rainbow' field added to transition screen, Status change fails. solution: remove 'Rainbow' from transition screen.
When transition is done by not using a transition screen, 'Rainbow' field has no limiting effect on Status change.

Thanks for your quick response. Issue can be Closed now.,

Deniz Oğuz
March 15, 2016, 12:40 PM

Plugin is now available in the marketplace. Please try to disable/enable the plugin. If you are still getting the error please check which plugin module is disabled as shown in the following screenshot.



Deniz Oğuz


Hubert Gabel





Jira Version


Database Type/Version


Browser Type/Version


Fix versions

Affects versions