can we have Contexts and Default Values option for other system fields other than Description?

[Moghal Jameer]

I would like to have Contexts and Default Values option for other Fields like Security Level and Created and Updated etc..

[Nic Brough -Adaptavist-]

I am a little confused.  Description, Security level, created and updated are all system fields, they do not have contexts.  Created and updated do not have default values either, they're set and updated by creating and updating Jira.

Custom fields do have contexts, and some accept default values.  The contexts are all set in admin -> issues -> custom fields -> <each custom field>, and the context includes the setting for a default.

But... I may be completely misunderstanding the question.  Could you explain more please?

[Moghal Jameer]

Hello Nic,

Thank you for your response.

My scenario is, I am importing some data to Jira. But the system fields are not getting visible on Field Mapping Page even the fields are included in screens.

So what i did is, I had created the custom fields ( Like in System Fields ) and added in screens. In this scenario The system fields data is not getting updated with correct data.

Please assist me. If you need any clarification, please reply back.

Regards

Jameer.

[Nic Brough -Adaptavist-]

I think this would need to go to Atlassian - the system fields are always available for mapping in the imports for me (at the top of the list, rather than mixed in with the alphabetically sorted custom fields), on server and Cloud.

If you're not seeing them in the list, then there's a fault in your system somewhere.  Whether they are on screen or not is irrelevant to the import.