how to use getIssueFields routine in jjupin for the current issue?

[eric anier]

Hi,

i could use this routine getIssueFields to get fields of the parent task by using parent.key as parameter, but what should i use to access the fields in current issue, im coding SIL for live fields by the way.

my code..

string vRetVal;

string[] fields;

fields = getIssueFields(parent.key);

vRetVal = fields["reporter"];

return vRetVal;

Thanks,

eric

[Silviu Burcea · Accepted solution]

string[] fields;

fields = getIssueFields(key);

key is a standard variable. You can find the rest of them here: http://confluence.kepler-rominfo.com/display/SIL/Variable+Resolution

[Alexandru_Iacob]

You can access the current issue fields by using the standard variables defined in SIL.

For example to retrieve the reporter for current issue you just have to use the standard variable reporter. For custom fields, you can access them either by id (eg. customfield_xxxxx) or by name.

For more details check this documentation page: http://confluence.kepler-rominfo.com/display/SIL/Variable+Resolution

Note that standard variables can be used without explicitly referencing the issue only when the script has an issue context, so not on create issue for example.

So, if you want to access some fields values on the create issue screen also, you have to use the live fields lfInstantHook routine: http://confluence.kepler-rominfo.com/display/JJUPIN/lfInstantHook

You have to provide the list of fields that you are interested in and a hook script in which you can access the value for these fields, using argv["<field_name>"].

If you want to get some field values from the screen after certain events (eg. changed, keyup), you should use the lfWatch routine for that field: http://confluence.kepler-rominfo.com/display/JJUPIN/lfWatch

Hope this helps.

[eric anier]

hi,

it seems that there are custom fields that can't be identified by the code below, tried using the equivalent customfield_XXXXX and it works.

vRetVal = fields["reporter"];

Thanks a lot,

[Patrick Riegler]

Hi Eric

Yes, it does not work with some of the custom fields.
Did you find a solution to the case?

Thanks for your help.

Regards
Patrick