Is it possible to:
Currently we have no official support for Profields. The problem is that for sure some of the fields will work (because we're trying to guess other CF's capabilities). However, the normal thing would be for us to write custom fields descriptors (JJupin uses some descriptors to translate the values from jira to the script and the other way around http://confluence.kepler-rominfo.com/display/JJUPIN/SIL+Custom+Field+Descriptors )
If the number has a simple representation ( java.lang.String or a java.lang.Number subclass) JJupin should be able to guess it. If the value is wrapped in some profield class, it will not guess it.
You should see it there (last time I checked, there were all the CFs descriptors listed there), but it should be mapped on "default" which really means "guess" :))
Edit: I was talking nonsense! I just downloaded it and I really do not see any customField in this plugin. Mea culpa. Most probably, you will need some custom development for this to work.
The fields are located within tables in the primary JIRA database. On my instance of JIRA, the field names are in a FIELD table (table name is prefixed with what looks like a unique prefix). A field scheme name is in a SCHEME table. A SCHEME_FIELD table maps which fields from the FIELD table belong to a defined scheme. A PROJECT_SCHEME table defines what projects have what scheme. A PROJECT_VALUE table then defines the values for each of the fields. Ultimately, what I'd like to do is get the value of a project field based upon the project an issue belongs to. This can probably be done with a SQL query. For example, if I had a Profield named "Account Name" and wanted the value of this field for a project with project ID 11801... I could use the following SQL query...
SELECT value FROM `AO_00B950_PROJECT_VALUE` WHERE `field_id` IN (SELECT `id` FROM `AO_00B950_FIELD` WHERE `name` = 'Account Name') and `projectid` = '11801' ORDER BY `projectId`
Is there any way to do this in JJUPIN?
Regarding script runner... ideally they would publish a component and have a documented API. I don't use that plugin so I don't know.
If they don't, then it's a case of grabbing their classes using the plugin classloader and trying to work things out from the method names.
We are evaluating a bunch of improvements of Profields for the next releases. If you don't mind, you can submit your request at http://www.madeira20.com and we'll explain more carefully the Profields roadmap for the next sis months.
At this time our short term priority is making Profields JIRA 6 compliance, but the next release period (May-August) should include several improvements (one of the user stories to evaluate is the ability to copy Profields Schemes, but we have to prioritize the user requests).
Thank you very much for your feedback.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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