-
Type:
New Feature
-
Status: Done (View Workflow)
-
Priority:
Trivial
-
Resolution: Duplicate
-
Affects Version/s: 5.5.9.1-jira8
-
Fix Version/s: None
-
Component/s: Scripted Fields
-
Labels:None
-
Critical Points:0
Let me share feedback on this new feature. I hope you'll find it useful and some of the ideas will be considered in future development.
My current use-case is that I have special field Versions containing all project versions in the whole Jira. It's great I can create hyperlinks to respective versions!
SELECT pv.ID, CONCAT( '<A HREF="/projects/', p.pkey, '/versions/', pv.ID, '" TITLE="', DATE_FORMAT(pv.RELEASEDATE, "%d/%b/%Y"), '">', pv.vname, '</A>', ' <FONT COLOR="silver">(', p.pkey, ')</FONT>') FROM projectversion pv LEFT JOIN project p ON p.ID = pv.PROJECT WHERE pv.ID = ?
SELECT pv.ID, CONCAT(pv.vname, ' (', p.pkey, ')', IF(pv.ARCHIVED='true', ' [archived]', '')) FROM projectversion pv LEFT JOIN project p ON p.ID = pv.PROJECT WHERE LOWER(pv.vname) RLIKE LOWER(?) ORDER BY pv.vname, p.pkey
Missing context
For certain use-case I would appreciate to have local context (project/pid, issue type, status) so that I can adjust SQL query accordingly.
E.g. something like this:
SELECT pv.ID, pv.vname FROM projectversion pv WHERE pv.PROJECT = ${issue.pid} AND pv.vname RLIKE ?
Notifications
E-mail notifications always display the ID. Although Jira stores IDs I'd like to display real values in notifications – the same Jira sends notifications about updated FixVersions (stored as IDs, but real values are displayed in notifications).
Incorrect format when searching
My values are formatted with HTML tags - awesome BTW. However, these tags are displayed at existing issues. See screenshots.
Unable to search fields
Fields have no search templates and it's unable to search via this field.
Invalid rendering of Database Picker field in Issue navigator for unsupported fields
CF context is not defined for this field at all and still the error is displayed.
Minor problems
- Database Picker custom field type is listed under Standard and not under Advanced when creating a new custom field.
Any response to my feedback appreciated
- duplicates
-
SRJIRA-3996 Allow Database Picker Fields queries to allow a value to be specified from a field on the issue.
-
- Done
-