This is a product defect, not a feature request.

When a user types a comment in a Jira issue but does not submit it and closes the issue/tab, the comment content is retained. If the user later revisits the same issue, the previously unpublished comment reappears in the comment editor. When the user submits this comment later, it is published with an older timestamp corresponding to when the draft was originally typed, instead of the actual submission time.

This results in incorrect comment timelines and can confuse users reviewing issue activity.

Environment

• Platform: Jira Cloud

• Browser: Chrome (also reproducible in other browsers)

• OS: macOS / Windows (not OS-specific)

Steps to Reproduce

1. Open any Jira issue (User Story / Task / Bug).

1. Scroll down to the Comments section.

1. Type a comment in the comment input box.

1. Do NOT click the Enter / Comment button.

1. Close the issue or browser tab.

1. After some time (for example, the next day), open the same issue again.

1. Click inside the comment box.

Actual Result

• The previously typed but unpublished comment is still present in the comment box.

• When the user edits the text or directly clicks Enter / Comment, the comment gets published.

• The published comment shows an older date and time, corresponding to when the comment was originally typed (drafted), not when it was actually submitted.

Expected Result

• Draft comments should not persist indefinitely without explicit save indication,
  OR

• When a cached/draft comment is finally submitted, Jira should display the current date and time of submission, not the draft creation time.

Impact

• Causes confusion and incorrect comment timelines.

• Comments appear to be posted in the past even though they were submitted later.

• This can affect audit trails, collaboration clarity, and issue discussion accuracy.

Why This Is a Strong Bug Report

• Clear reproduction steps

• Real user impact

• Timestamp inconsistency = data integrity issue

• Very valid for Jira product teams