Cycle time on Control chart showing 1w 6d when a week should be 5d long

[Louise Griffin]

My control chart is showing an average cycle time of 1w 6d 9h (non working days unticked) but the working days are configured as monday - friday (5d). Shouldn't this show 2w 1d 9h?

There is another question like this but no definitive answer https://community.atlassian.com/t5/Jira-questions/Control-Chart-Average-Mixing-Weeks-amp-Days/qaq-p/609649 

Can anyone help?

[Marcus Silveira · Accepted solution]

Hi William,

As Jessica mentioned, JIRA doesn't add watchers during a "regular" issue creation, which means that the issue created via email first creates the email (which triggers the Issue Created event and notification) and only after the issue is created the watchers are added.

We have JRA-5493 to add this feature, but there's no ETA on that yet.

[James King]

Marcus, we use Autowatch Rules for issue types that are created from email automatically generated by our various platform and system alerts, and have the same resulting problem. Your answer elaborates on the cause of the problem (the sequence of events), then links to an issue that outlines a different problem. We *have* Autowatch Rules as an option, now, or can add watchers at issue creation through the Cc field. That issue is solved for many scenarios, thus reducing the urgency of the original request. What is not working is a notification that should go to the watchers surrounding an issue creation notification. The former is a feature request, and the latter is the failure of a feature (or combination of features) to operate as expected. Even the [information provided on the Marketplace about Autowatch|https://marketplace.atlassian.com/plugins/com.atlassian.addon.connect.jiraautowatch] suggests that users are added as watchers, and issue creation notifications go out to those watchers. While I understand that this is in queue for future development, it needs to be escalated.

[Jessica_Moszkowicz]

I don't believe you can assign watchers from the issue create screen. Instead, I think the thing Atlassian would rather people do is use @mentions in the description of the issue. This will send an e-mail out to people and then they can visit the issue to become watchers on it themselves, or you can make them watchers after you create the issue. To make sure that the e-mails go out during issue creation though, you need to mention those users in the issue description. Hope this helps!

[Jeffrey Gordon]

A similar issues occurs with comments.  The first time a user comments on an issue they don't get an email.  However, by adding that comment they are added as a watcher and will get emails for subsequent comments/changes.

This is assuming you have "All Watchers" for various events in your Notification scheme.