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

Support-Task admit StoryPoins value?

Jorge_de_Carlos

Hello,

Our project included Bugs, Stories and Support-Task. The value of StoryPoint doesn’t appear from Suppor-Task issues.

Can someone explain us? Is a problem of SupportTask configuration or Support-tasks do not admit this value (Estimate as StoryPoints)?

Regards,

Jorge.

Accepted answers

Tarun Sapra

Hello @Jorge_de_Carlos

Story points is just a normal custom field and that's it!

Thus, as any other custom field you can map the custom field to "SupportTask" issueType and it should work easily.

Please see how to configure custom field

https://confluence.atlassian.com/adminjiraserver071/configuring-a-custom-field-802592532.html

If you have admin rights then you can directly add the custom field story points from the view screen of the SupportTask issueTYpe

https://confluence.atlassian.com/adminjiraserver071/adding-a-custom-field-802592519.html

And once story points is added to the supporTask issue then you can also put estimates on this issuetype if the issuetype is present on your board and the board has the estimation configured to be story points.

All comments

Tarun Sapra

Hello @Jorge_de_Carlos

Story points is just a normal custom field and that's it!

Thus, as any other custom field you can map the custom field to "SupportTask" issueType and it should work easily.

Please see how to configure custom field

https://confluence.atlassian.com/adminjiraserver071/configuring-a-custom-field-802592532.html

If you have admin rights then you can directly add the custom field story points from the view screen of the SupportTask issueTYpe

https://confluence.atlassian.com/adminjiraserver071/adding-a-custom-field-802592519.html

Jorge_de_Carlos

Thank you very much @Tarun Sapra,

I have another question: when a ticket is developed, we move it to "Done" column (Active Sprint) because we don't want to keep there on the Backlog. However we need to keep the control about these tickets before going production.

Any idea?

Regards,

Jorge.

Tarun Sapra

Hello @Jorge_de_Carlos

Your question is very broad and it depends on how your teams works. Generally you can choose todo either of the two things for tracking the ticket to production

Extend the workflow to add release specific status like "Ready for UAT", "In UAT" , "Integration testing", "Ready for Prod", "In Prod". Thus once the story is done then for scrum team it's done but the release team can have the kanban board with these statuses where the story can be tracked. Thus once the story reaches right most column on scrum board then make that status as left most column on release kanban board.
Another approach is that when the story is done by scrum team then in the transition post-function you can create an linked ticket ("release") for the release team in the project used by release team and thus track this newly created release ticket

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-service-desk