1. Atlassian
  2. Project: Atlassian
  3. jira-fisheye-plugin


jira-fisheye-plugin /

Filename Size Date modified Message
145 B
FECRU-5749: use render to show "unlicensed" message
4 B
FECRU-5747: post-review, remove duplicated plugin-info
1.5 KB
Removing whitespace
2.4 KB
README.md edited online with Bitbucket
33.7 KB
JPA-2851 : Remove maven version override for ATSLATs

JIRA FishEye Plugin

Repository branches

Branch JIRA version
jira-fisheye-plugin-5.0.x JIRA 5.0 - 5.1
jira-fisheye-plugin-5.2.x JIRA 5.2
jira-fisheye-plugin-6.0.x JIRA 6.0
jira-fisheye-plugin-6.1.x JIRA 6.1
jira-fisheye-plugin-6.2.x JIRA 6.2
jira-fisheye-plugin-6.3.x JIRA 6.3 - 6.4 (Java7)
master version in development, needs to be cut into jira-fisheye-plugin-x.y.z when superseeded, currently JIRA 7.0 (Java8)

More info: https://extranet.atlassian.com/display/FECRU/JIRA+FishEye+Plugin+documentation+and+release+procedure


Current master should build against JIRA 7. CI builds are at https://server-gdn-bamboo.internal.atlassian.com/browse/JFP:



mvn amps:debug -DinstanceId=jira

will start only Jira instance. In order to force JFP tabs to be visible (in parallel to Fusion plugin), enable dark feature flag as follows:

mvn amps:debug -DinstanceId=jira


mvn amps:debug -DtestGroup=integration-tests

will start a JIRA instance, and two FishEye/Crucible instances. This is the environment used by func tests. By default no applinks are set up, the tests create (and teardown) them as needed.

Fecru data is restored from AMPS zips on startup (from fecru-test-data.zip). JIRA data is restored once when starting tests (from jira-test-data.zip). Avoid restoring extra data during tests and make sure tests clean up any changes after they're done (applinks, issues, etc.).

Run func tests locally using

mvn integration-test

Dark feature

In order to force JFP tabs to be visible (in parallel to Fusion plugin), enable dark feature flag by adding the following maven parameter: