nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I create a template in Jira so the requestor includes specific information in the TLE creation?

Mike Boutin

I am looking to create an intake method for a requestor to include specific data in the creation of a TLE.

Would it be possible to have a template or an existing TLE that they could clone?

Based on their response I could have automation to generate standard stories depending on work request type.

Are there other ways to implement this?

Accepted answers

All comments

Valerie Knapp_gp7rpj

Hi @Mike Boutin , thanks for your post.

What is a TLE please?

You can have different create screens for different work item types and then with the field configuration, you can make some fields mandatory, for example.

https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-a-field-configuration/

https://support.atlassian.com/jira-cloud-administration/docs/add-a-custom-field-to-a-screen/

Does this help you at all?

Cheers

Mike Boutin

TLE = Team Level Epic

Sample:

I am looking to have this either as a default that can be selected or a Template that can be cloned.

Marc -Devoteam-

Hi @Mike Boutin

Based on your description you will have to createca new custom field, based upon a multi-line field.

In this field you can set a default. set this field on the create screen used by the TLE and remove the default Description field from the screen.

Keep the default description field on the screen or screens used for edit and view.

Create an automation rule based on the creation of a TLE copies the value of the new description fiel to the original description field.

Mike Boutin

@Marc -Devoteam- Thanks. I want to avoid custom fields if at all possible.

Mike Boutin

@Valerie Knapp I am trying to avoid custom fields at all costs.

Marc -Devoteam-

Hi @Mike Boutin

This is not possible without a custom field or a 3rd party integration.

The ootb description field can be used for such a requirement.

The only other option I see is to create an issue/work item with this set as a default an clone that issue every time.

But this is not a best practice and still requires you or the requestor to clone this issue first and then use it.

You would need to anker this into your process.

Valerie Knapp_gp7rpj

Hi @Mike Boutin , I agree with @Marc -Devoteam- that you will need a custom field to do this. I understand that you don't want to create new / excessive fields but if you need it to do something, you need it to do something.

Best wishes

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud