I cannot figure this out, and have searched the Answers board thoroughly...
Problem statement: Why is GH seeking an estimate for some issue types, but for others, it does not look for an estimate? If I try to start a sprint without an estimate for the few that GH says must have an estimate, it warns me.
1. Goto test project project.
2. Goto Agile >> Paul Test board in greenhopper. Notice in configuration that I am using Story Points as the Estimation Statistic, while I am using Remaining Estimate and Time Spent for Time Tracking.
3. Notice that I have a sprint ready to go called Gonzo 5 on the Plan view. There are (7) total parent issues in the sprint.
4. There are (3) Story issue types (TST-49, TST-163, TST-219), with a story point estimate of 2, 7, and 5 respectively...see attached screenshot. These are correct since I use story points for stories...time remaining for each of these three stories is 4, 4, and 9 hrs respectively...This is also correct.
5. There is (1) Development Bug issue type (TST-167), and the UI is not expecting an estimate value...this is correct because I do not use story points for this issue type. There is 21 hrs of work remaining...this is also correct.
6. There is (1) Admin issue type (TST-174), and the UI is not expecting an estimate value...this is also correct because I do not use story points for this issue type. There is 2 hrs of work remaining...this is also correct.
7. Lastly, I have (2) PS Incident issue types (TST-185, TST-206). The UI is expecting an estimate value....WHY?? I do not use story points for this kind of issue type (just like steps 5 & 6 above). There is 4 and 3 hrs of work remaining respectively...this is correct.
8. Click Start Sprint and notice that the modal is warning me that the two issues (see step 7 and attached screenshot) do not have estimates.
Summary, why does GH want an estimate for step 7 above, but it does not care about the issues denoted in steps 5 and 6 above?
Thanks for your time. I have setup other scenarios, but cannot get this to work...I'm working hard to assure I can use and train folks to utilize the new GH boards as I try to cut over from Classic boards, and I'm having a heartache with this;).
Just wanted to follow up here in case anyone else runs into this problem. Took me a little while to track down, but it seems like the issue is related to having your Story Points field associated with the PS Incident issue type. You can get there from custom fields page, and if you go to Story Points and Edit Configuration, you should be able to remove that.
Yes, bonehead user error. Dave hooked me up, but a little extra flavor for those still mulling this over, if I may...
Just because an Issue Type is not used on a Screen does not mean it will not be interpreted elsewhere...this is an example. The Field in question is not used on my Screen, but at some point in the past I had assigned this Issue Type as being used by this Field. So, the new GH Boards expected a value from that Field.
Wheew. Glad that's behind me now. Kudos, Dave!
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello and happy Topic Tuesday! We would love to continue to find out more about you. Here’s the question: What is one way Atlassian products have shifted the way your team works? Looking forw...
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