The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Hide Summary field, make it as non-editable and update Summary through PostFunction

Binisha
Contributor
January 7, 2013

Hi All,

My requirement is to make the Summary field non-editable for one particular issue type.

1. A text field called "customsummary" is added to the create screen

2. The Summary of the issue Type shall not be editable by the user

3. When the issue is updated the Summary field shall be updated according to the format

[Value in Customsummary][Jiraissuekey]

Please let me know if there is any feasible solution for this

Thanks

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Renjith Pillai
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 7, 2013

Or simply swap the usage. Keep summary as it is and create another Scripted Field (using script runner plugin) which always returns you this value [Summary][Issue Key]

Binisha
Contributor
January 8, 2013

Thanks Renjith.

Let me consult the reporter for this.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 7, 2013

This will not work. You must enter a summary as you create the issue.

What you CAN do is write/find a plugin that will update the summary after the users commit the creation.

If you really do want something that automatically generates it, I'd also add javascript to the create screen to pre-populate the summary with something like "Automatically generated summary, please leave this here".

If you're planning to auto-generate the summary based on what they entered in your customsummary, then I'd forget it - let them enter the summary as normal, and then the post-function will have what they've entered available and can simply change it instead of processing two fields.

If you want to disable it completely, or even just make it optional on create, you need to amend the core code.

Binisha
Contributor
January 8, 2013

Hi Nic,

Thanks for the reply. I will try to do any of the suggested methods.

TAGS
AUG Leaders

Atlassian Community Events