I am looking for an add-on that will allow me to create a custom field, similar to "issue Links".
I need to be able to perform the following actions:
* Limit the selections of issues based on a custom filter
* Add a work flow validator to prevent the issue from moving states, if the linked issues do not meet a specific criteria
* Have the ability to rearrange the order of the issues that are linked (Similar to a ranking)
Any suggestions on a plugin that will allow this would be appreciated.
I've never seen a plugin that's even close to the built-in issue linking, they're all less functional.
Your middle requirement though - there's several validators in the marketplace that will do that. And, there's always the script-runner plugin.
Using the built-in linking, I can already address the middle requirement. What I am attempting to do is ensure is to limit what issues can be marked as blocks and what issues can be marked as related to.
I have built filters for these conditions, however, I want to enforce the use of the filters when adding the links
I have looked at an add-on "issue picker", however, you cannot enforce a search filter.
The 3rd requirement for supporting a ranking order is nice to have at this point
You're going to need some code for this. I'd look at a new "custom field type", and start with https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Guide- it's got a load of links - most you won't need, some you can skim and you'll want to concentrate on "plugin guide", the stuff that explains how Jira works and then the custom field/searcher modules
I have made significant progress on building my custom field. I am hoping you can suggest how to get by 1 critical issue I have having.
I built a custom issue picker, based off of type MultiCFType <String>. I am able to add values using an issue picker search, and retrive the values successfully. I have modifed my velocity templates to handle the appropriate formatting.
The 1 issue I am struggling with is the order of the values within the field. In my example, I select issues from my query and store the values of FR-5, FR-3, and FR-6 in that order. when the values are saved, they are stored as FR-5, FR-6, and FR-3.
Do you have any reference to the methods used to write to the database, and why the order would be altered? I have added debugging, and the data is returned from the velocity templates properly.
I doubt it's anything to do with the database, I suspect it's the way the data is fetched. For a multi-select list, the database just holds a pile of records for it. The Java fetches it back in some form of list object, unsorted. It's expecting the code that uses the result to do the sorting (no point in sorting if it's not needed or going to be overridden)
Best bet is to put some form of sort into your Java or even display template
Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG