Category (Locked) field and Populating through automation

[sheradyn.ford]

Hi All,

I'm trying to populate the recently introduced Issue Category field on Work Management Projects through an automation.

I have a cascading dropdown box configured that the users populate during issue creation. I was able to extract the level 1 value of that dropdown into a single line text field, however upon finding limitations in the filtering/grouping of the work management list view - am now trying to move the value from the single line text field to the Category field.

I've already added all the context options that could possibly be entered in that field through the automation, but I'm getting errors.

I've also tried populating the Issue Category field directly from the cascading dropdown, as well as from the Single Line text field I had originally configured.

It won't let me configure this through the simple method, so having to use advanced and I'm not very familiar with JSON coding.

Any help would be massively appreciated.

---

Fields:
issue.customfield_10070 = Cascading Dropdown box providing value
customfield_10084 = Single Line text field originally configured to take the value from the cascading dropdown.
customfield_10080 = Issue Category (Locked) field trying to populate

---

WORKING CODE
This is the code that is currently writing to the single line text field.

{
"fields": {
"customfield_10084": "{{issue.customfield_10070.value}}"
}
}

---

NOT WORKING CODE
This is the code that is not working

{
"fields": {
"customfield_10080": "{{issue.customfield_10084.value}}"
}
}

[Deleted user]

As discussed at http://confluence.atlassian.com/display/JIRA/Customising+Email+Content

You could use http://code.google.com/p/veloeclipse/, I have it but find it half works half annoys, the selects dont work as they do with Java code, selects multi-line content when I want the quote delimited field.

Anyway, there are no plugins that provide editing over all templates. To do assumes some things (a) that JIRA is standalone (not WAR) packaged, (b) that the running user has permission to actually modify the files (possible, but perhaps the files would be readonly), (c) that the files get cached for performance, meaning you won't be able to see result until you reboot. All in all, why write a plugin?

You're best off with notepad or similar in a DEV Jira, editing the templates directly, after disabling velocity caching.

The 'enabling' factor here would be if Atlassian addressed https://jira.atlassian.com/browse/JRA-19957 allowing YOU to disable /remove the default IssueListener and substitue your own. Potentially, this then allows custom editing through plugins, similar to what I've done with JEMH for its templates.