Description:
Currently, when a Slack thread is converted into a Jira issue or added to an existing one using the Jira Cloud for Slack integration, the comment timestamps in Jira reflect the sync/import time (the moment the data is written to the Jira database) rather than the original Slack message creation time.

This behaviour causes several critical issues for users:

1. Loss of "Source of Truth": In a fast-moving thread where multiple solutions are proposed, all comments may appear with the same or very similar timestamps in Jira, making it impossible to determine the actual chronological flow of the decision-making process.

1. Search & Audit Inaccuracy: If a user searches for comments made "Last Week," but a Slack thread from that period was only synced to Jira today, those comments will not appear in the search results for the correct timeframe.

1. Data Integrity: For auditing purposes, the lack of original timestamps breaks the historical fidelity of the communication.

Suggested Functional Change:
The integration should capture the original Slack message timestamp and either:

• Map it to the Jira comment's Created field (if system constraints allow).

• Or, provide a dedicated "Source Timestamp" metadata field/display within the Jira comment UI to show when the message was actually sent in Slack.

Expected Outcome:
Jira comments should accurately represent the original timeline of the Slack conversation to maintain chronological integrity and support accurate auditing.