We have been running our project for a few weeks and closed off a number of agile (greenhopper) issues yet this chart is showing 0 unresolved.
Our issues do not contain any time estimates but only user points. We always Resolve the issue by dragging into into the final field on the Agile Task board, though some we have closed using "Resolve Issue"
Looking around I can't find the answer but there was a similar question so if this helps: our Resolution field is set as hidden by default.
Any help would be appreciated.
Maybe you can set the gadget to bring the information from a filter. A filter that of course will have "resolution = null", so it shows every issue that doesn't have a resolution, even if that field is hidden.
I'm not sure thats the answer to be honest, though maybe I don't understand this well enough. How would I do that?
For instance I go to my Project Summary, then click Reports, select "Created vs Resolved Issues Report", I select the project, the period and show all versions before clicking Next. On the resulting graph I see the springs and the issues, but 0 are resolved.
I look at the versions then and the stats on the planning board show 0 resolved, however the list on the left shows each story along with the status as "Resolved". If I view the workflow I can see it as "Resolved" though not marked as "Closed". To my understanding thats the same thing though, as we drag it to the last column on the task board.
Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just done a test on the issues, I selected "Close" though this doesn't do anything other than mark it as "Closed". There are still 0 resolved items. So it confirms that Resolved and Closed are the same thing, though doesn't resolve my problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Exactly, I understand that Resolved and Closed are the same thing in matters for the "Created vs Resolved Issues Report". I have to say that this issue is very rare.
In cases like this I create a ticket in the Atlassian Support, I have experienced a great support from Atlassian and they respond very quickly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.