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

Business Value - ‘should be actually a default feature in Jira Software’

Sarath_28nbxy

Business Value has its own essence which when followed, the team is driven with absolute focus to deliver the features/requirements , which adds value to the customer’s product. This is also an Agile principle.

Hence I request the Jira to have an upgrade exercised, making business value as default. Advantage - If applied by Atlassian, HCL can promote to other accounts too and be flagged as following THE ‘Agile Principles’.

Accepted answers

Walter Buggenhout

Hi @Sarath,

Business Value IS a custom field available in Jira Software by default. The only thing you need to do in order to use it, is add the field to your screens and you are good to go.

All comments

Walter Buggenhout

Hi @Sarath,

Business Value IS a custom field available in Jira Software by default. The only thing you need to do in order to use it, is add the field to your screens and you are good to go.

Sarath_28nbxy

Thanks for your reply @Walter Buggenhout

My question Business value field made as custom instead of default fields such Summary, Story Point, Assigned User etc.

Since Business Value has its own essence which when followed, the team is driven with absolute focus to deliver the features/requirements , which adds value to the customer’s product. This is also an Agile principle.

Regards

Sarath

Walter Buggenhout

That is a good and valid point @Sarath.

At the same time be aware that once fields are on a screen, to a user there is absolutely no difference whether a field is a default field or a custom field. It is just something they need to fill out when they create or update an issue. So to them, it doesn't affect anything really in terms of user experience.

Considering that Jira serves many use cases outside of Agile software development and teams all over the world implement agile and other methodologies tailored to their own needs, enforcing the field as default would not be valuable in many situations. Business value is not a driving factor in e.g. an onboarding process for employees.

With the ability to adjust to change at the very core of what agile is about, I think having the flexibility to include the field when you need it and leaving it out when you don't is rather good than bad.

Welcome!

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

Quick Links

Find more posts tagged with

jira

business-value