set customfield on transition screen activiation

werner kolze June 28, 2015

hello there - 

I was wondering whether a customfield can have its value set, once the user presses the appropriate transition button, which is linked to a transition screen. 

I would like to pre-set a value once the screen is activated.
to elaborate:

After a user creates an issue, then several choices, in form of transition buttons are on the screen, say then the user presses the "Standard" button, a transition screen pops up and I want then a customfield called "Change Category" to be set to "Standard". I am using this in conjunction with the data gathered on that screen and I do not need it "AFTER" the transition button is pressed.

 Hope this makes sense

1 answer

0 votes
Andrii Mishak June 28, 2015

In our plugin we did it by two ugly enough methods:

  1. extend Custom Field class, and overrride methods to get value to view

    public class MyCustomFiled extends AbstractSingleFieldType<DomainClass> {
        @Override
        protected DomainClass getObjectFromDbValue(@Nonnull Object o)
        public DomainClass getValueFromIssue(CustomField field, Issue issue) {...}
    }
  2. Use JIRA.Events.NEW_CONTENT_ADDED event

    JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function () {
        var issueTypeFields = document.getElementsByName('issuetype');
        if (issueTypeFields) {
        var issueTypeField = issueTypeFields[issueTypeFields.length - 1];
        try {
            if (issueTypeField instanceof HTMLSelectElement) {
                if (issueTypeField.options.length) {
                   ...
                }
            }
        } catch (e) {
        }
    }

The thing is what our custom fields default values are depend on another custom fields values...

werner kolze June 30, 2015

what is your plugin? do you need to update the custom class every time you update Jira? the snippets here dont make quite sense to me, sorry, I would not know where to take this from here

Andrii Mishak June 30, 2015

It is internal plugin, we do not publish it. First one is creation special custom field type. Second one is jQuery hook on page load.

Suggest an answer

Log in or Sign up to answer