In Agile it's possible to add multiple fields to the detail view (see the screenshot on https://confluence.atlassian.com/display/AGILE/Configuring+the+Issue+Detail+View).
Question:why would you want to add fields that are not defined in the underlying JIRA screen/field settings?
In other words, an added field will be shown in the Agile interface (issue detail view), however in the first place it could/can not be entered when creating an issue, and then, it cannot be edited - because the field is not defined in the Create and Edit screen/field definitions. What is the logic behind this possibility? I would say it's more logical to choose only fields that make sense according to the underlying (screen/field) settings in JIRA.
1. It's a lot of work to decide whether a field should really be there based on all the possible combinations, then you have to decide what to do if the field visibility is changed - e.g. if you remove field X from a screen, do you automatically remove it from the Agile view? What if there's a mistake and you put it back? Expect it to automatically reappear in Agile?
2. There are reasons to have access to fields that the user does not update. One really obvious example - bugzilla import id field. Not on create or edit screens, can't be edited, just imported.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG