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; } } }

Estimate column for issue types?

Sam_w4yoj1

Can we have separate estimate options for issue types.

Story point for Story,

Original Time estimate for Task

In the same project in JIRA cloud.

Accepted answers

Alexey Matveev

You can use different estimation for Story and Task (add proper fields on the create, edit and view screens). But for a board you can choose either story or original estimate.

All comments

Alexey Matveev

You can use different estimation for Story and Task (add proper fields on the create, edit and view screens). But for a board you can choose either story or original estimate.

Sam_w4yoj1

Can you please tell me the process to add story point field to all the issue types except Task and original time estimate to task.

Thanks,

Sai.

Alexey Matveev

You should create diffrent screens for the Task issue type and for all other issue types. For the Task issue types there will be the original estimate field and for all other issue types there will be the Story points field.

You can find more info on how to create screens here:

https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html

After you created the screen, you should associate the screens with the proper issue types. You can find more info here:

https://confluence.atlassian.com/adminjiraserver073/associating-screen-and-issue-operation-mappings-with-an-issue-type-861253453.html