-
Bug
-
Resolution: Timed out
-
Medium
-
3.0.3, 3.2.4
-
None
-
Severity 2 - Major
-
0
-
Lets say you want to create a review from a commit. You can do this two ways:
1. JIRA issue source tab, click on Create Review button.
2. Fisheye news feed, click on the Cogwheel icon on a commit and create Review.
Crucible will automatically add a Link To.. option that helps the user to link back to the JIRA issue in the review. This does not work when that issue belongs to a project that has a custom project key pattern, e.g.:
TBK2-10200
This works normally if the project key pattern is the default JIRA one.
No errors thrown in the logs for both JIRA and Fisheye.
Tested on the follow sets of installations:
-------------------------
JIRA 6.0.8
Fisheye Plugin 6.0.2
FeCru 3.0.3
-------------------------
JIRA 6.1.6
Fisheye Plugin 6.1.6
FeCru 3.2.4
- relates to
-
FE-4719 Some custom JIRA issue key patterns not linked in activity stream
-
- Closed
-
Also with transparency - the criteria you are using is entirely invalid:
As far as I am aware - this issue remains relevant. Did you try it before concluding anything here?
The real conclusion here is that you don't want to look into this issue, and the above logic blames the users for what amounts to an Atlassian failing. I normally ignore these, as I understand that it's difficult to manage a roadmap with limited resources - but the Crucible roadmap has seemed pretty dead, and it feels disingenuous to see messages such as the above that try to dress up "Won't Fix" as-if the users are at fault here. In our case - we have been seriously reconsidering whether Crucible/FishEye should be part of our solution anymore given the extremely low trickle of features and bug fixes that Atlassian has been addressing.