I have seen the answers No to my question or similar question but I want to explain why it is needed to enable the Project Summary page to be configured.
As you can see there is a gadget there (Issues: 30 Day Summary) shows CREATED issues versus RESOLVED issues. also we know there is a state after RESOLVED as CLOSED. If I use CLOSED state the gadget will not work properly. It always shows some CREATED but zero RESOLVED.
This gadget works correctly for JIRA default work flow, not even for RESOLVED issues but also for CLOSED issues. So I tried to use default workflow and just modify it then see the result. Unfortunately it did not worked.
Therefore, I suggest to make configuration for project summary and let administrating that. Other requests regarding to the case I mentioned can be reviewed and resolved.
Thank you very much
The gadget works fine for the default workflow, I'd suspect that you're misunderstanding what it's for. But you don't really explain what you think is wrong with what you are seeing there.
Rather than ask to configure something that works for most of us, could you explain what is wrong?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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