I'd like two sections for estimates (broken up with a divider). The first section should be called P50 Estimates, and needs two fields: P50 Dev Estimate, and P50 Test Estimate. The second section should be called P90 Estimates, and also needs two fields: P90 Dev Estimate, and P90 Test Estimate.
You haven't bothered to tell us which system you are talking about, or given us much else in the way of describing the field/fields layout or display. Or what you've got now.
Please clarify your question, and in a way that describes what you want properly.
What do you mean by "have field 1 under field 2"? Have you tried working with the standard "cascading select list" yet?
I ask because it's a good baseline - if you test a certain type of field, you can then tell us if it works for you, and/or what it needs to do differently. This is easier than a requirement plucked out of the air with no starting examples.
That's still not enough to work with really. "almost similar" - what needs changing? "enter values" - er, that's what you do with fields. "shouldn't be select list" - ok, but what should it be? You mention text in your question, but that's nonesense when talking about select lists?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs