I am evaluating JIRA Client v3.5.1 add-on on JIRA v6.1.5 instance. I am working offline on my JIRA tickets i.e., creating/transitionin status, via JIRA Client and then later when the JIRA server is up and running, the tickets are synchronized.
But upon synchronizing the offlince tickets from JIRA Client to JIRA server, the actual timestamps of the tickets are not transmitted instead the synchronization time is being considered as the actual timestamp for the tickets and are updated in JIRA server.
Also, while transitioning the issue, the timestamp populated during the post-functions while transitioning the ticket must transmit the actual timestamp rather than synchronization time as the actual timestamp.
How can the actual timestamp of an ticket updated offline be transmitted from JIRA Client to JIRA server. Can anybody share the approach on this issue.
I'm sorry for delayed reply; somehow we missed your question on Answers.
If I understand correctly, by "timestamp" you actually mean the "updated" date on the server and in the issue history. Unfortunately, we can't do much about it. For JIRA server, the update happens when JIRA Client uploads your changes. There's no way we can override that time and "insert" an update into the past. Sorry if that is an inconvenience.
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