Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,368,685
Community Members
 
Community Events
168
Community Groups

summary value should be change by given issue type in jira

Edited

Hi team 

need a help on creating a

Summary value should be change by given issue type in Jira. Summary it consists  type of  issue type must be include  .

example like 

Project name: Jira Test

Key  :JT

Issue type :Story, Bug, 

while  creating any issue type need to be in summary like this  " JT-1 Story, JT-2 Story, JT-3 Bug. JT-4 Bug"

 

can you please help on this any one,

 

Thank you

2 comments

John Funk Community Leader Apr 01, 2021

Hi Vasanth,

You can do that using an add-on like Automation For Jira or JMWE or ScriptRunner. Do you have any of those? 

Hi @John Funk 

thank you for the response .

yes , I have these three .

can you please assist me how to use .

 

Thank you

John Funk Community Leader Apr 01, 2021

Sure - I would use Automation For Jira then. 

Create a rule based on Issue Created

Then add a New Action for Edit Issue

Select the Summary field

Then paste this in the field: {{issue.key}} {{issue.issuetype.name}}

See if that works for you.  :-)

Thank you @

 

I will try this approach 

Like John Funk likes this

Hi @John Funk 

can you please  let me know how it works in JMWE,ScriptRunner

 

Thank you

John Funk Community Leader Apr 01, 2021

For both of those, you would add a Post Function on the Create transition. Following the guidance of the app for syntax. I do not use ScriptRunner so I wouldn't be help there, but support from other app would be able to guide you. 

Hi @vasanth ,

using JMWE, you can add a Set Field Value post-function on the Create transition, with this configuration:

  • Field: Summary
  • Value Type: Constant or Groovy Template
  • Value:
${issue.key} ${issue.get("issuetype").name}
Like John Funk likes this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events