Clarification Needed: Inconsistencies with Start Date and Resolved Date Logic

[RITA DE CASSIA SANTOS SOLE]

I hope this message finds you well. I am writing to seek clarification regarding the logic applied to the Start Date and Resolved Date fields in your system.

We have encountered situations where users are able to change the Start Date to a date that is later than the Resolved Date. This alteration results in negative lead times, which significantly skews our performance metrics and affects our reporting accuracy.

Could you please provide insights into the rationale behind this functionality? Additionally, is there a plan to implement restrictions or validations to prevent such inconsistencies?

Thank you for your attention to this matter. I look forward to your prompt response.

Best regards,
Rita de Cássia Santos Solé
Agile Master
Claro Brasil

[Matteo Vecchiato]

Hi @RITA DE CASSIA SANTOS SOLE ,

Welcome to Atlassian community and thank you for your question.

This is the community where everyone, from Atlassian and not, can collaborate.

About your question: resolved date is set automatically when it han been set a resolution in the work item, independent to others date.

You can find the explanation here: https://support.atlassian.com/jira/kb/new-issues-are-being-created-with-the-resolved-date-set/ 

The start date hasn't an out-of-the-box logic and it is manually set. You can implement some custom logic, depending on the requirements.

There isn't any relation between those 2 fields.

I hope it clarify.