How to specify default value for each issue type for description field on a project?

[yeldar_kossynbay]

Hello

How to specify default value for each issue type for description field on a single project?

I have one project with Scrum board in it. I have issue types: Story, Task, Bug!

When __Analyst__ create a new ticket with type "Story" I want to give him predefined text template for full filling:

'''

Title: <describe a massive business value feature>

Description: 
Explain the business value of the feature:
As <who?>,
I want <what?>
so I can <why?>.

Done conditions:
<give a list of exact requirement>

 '''


and I have these template for each issue type. 

So how I can configure it?

UPDATE:

Before I wanted to have only one template for all issue types.
So: I have created a custom description field link with project as context and all issue types, and then linked with Field Configuration.

Now I need the different pre defined values for the field for each issue type.
So, I'm trying to created more field contexts to specify them for exact issue type. But those contexts is imposible to link with single project.  Because Jira hide project from the list.

Project A -> Custom field Description -> issue Story -> Value X (Template)

Project A -> Custom field Description -> issue Bug -> Value Y (Template)

Project A -> Custom field Description -> issue Task -> Value Z (Template)

[Florian]

You can use different worklflows for each issue type and add a post function update field on a transition. For custom fields you might need JSU as it allows a post function called update any field. Another way is to uses Automation for Jira and trigger an automation rule on create or transition. With Automation for Jira you can use a single workflow and create if/then/else branches. Both JSU and Automation for Jira are plugins in the marketplace.

[Denise_Wuethrich_beecom_products]

Hi, @yeldar_kossynbay ! @Florian is right. JSU allows a post function called update any field to be used for your use case. Checkout the documentation here for Jira Cloud: https://beecom-products.atlassian.net/wiki/spaces/JSUCLOUD/pages/27801878/Update+any+Issue+Field+Post-Function

[yeldar_kossynbay]

@Florian  @Denise_Wuethrich_beecom_products 

Beecom and Jira Automatisation works when I already submited ticket to be created. I think it's a bit different. 

Before I wanted to have only one template for all issue types.
So: I have created a custom description field link with project as context and all issue types, and then linked with Field Configuration.

Now I need the different pre defined values for the field for each issue type.
So, I'm trying to created more field contexts to specify them for exact issue type. But those contexts is imposible to link with single project.  Because Jira hide project from the list.

[Denise_Wuethrich_beecom_products]

Hi, @yeldar_kossynbay You might actually use a precondition but we're not very sure about the specifics of your case. It would be best to check out the documentation or submit a ticket on the service desk. 

Service desk:

https://beecom-products.atlassian.net/servicedesk/customer/portal/3/user/login

Preconditions:

  https://beecom-products.atlassian.net/wiki/spaces/JSU/pages/25680508/Workflow+Preconditions 

[Jarosław Solecki _Deviniti_]

@yeldar_kossynbay  Quite a long time since you posted but maybe you still struggle with such a problem. 

There were made few changes in how Jira works which allowed us to create solutions for teams that have a need of making a create screen more flexible and usable for users. One of the annoying problems has been screens that are not designed for the user context. We made a few improvements to help with that. One of the things we introduce is the ability to set Default Values for fields. We base here on the issue screen schemes so you just have to divide them and then you will be able to create different default values for each issue type you mentioned.

Moreover, you also gain some additional abilities like set value based on condition, and conditional show/hide fields, making them required or read-only. 

You can benefit from all those things with Dynamic Forms for Jira. If you have any questions or would like to have a demo session just book it here.