I'm trying to set up integration between TMetrics and JIRA and I do not know how to install the TMetrics Add-on. Is this already working?
TM Master, JIRA Slave. I expect it.
But what happens in worklogs when an error occurs as we solved that there is no synchronization. Does this mean that the changes during a power outage will not be transferred, even afterwards?
And my second question about the TM-> JIRA backward update? How is the update going backwards?
Here is how it works in a nutshell.
Time is not synchronized back to TMetric from JIRA. We don't mark work log items as created by TMetric. Thus, we cannot say whether a time entry was added from JIRA or deleted from TMetric.
If we borrow the database replication terminology, TMetric can be considered as a "master" and JIRA as a "slave".
This means the following:
Hm... The add-on integration record has disappeared from the database.
It seems strange. I'll pass the issue to the developers.
The workaround is the same - uninstall and install the add-on in JIRA (don't delete the integration this time).
You've deleted (you shouldn't) JIra integration in TMetric along with the addon. When you delete the integration, all time entries are unlinked from external tasks.
There is a manual workaround for restoring the links (must be followed by users for their own tasks):
We've added to our backlog auto-linking for previous time entries after the first step. We'll tackle this problem as soon as possible.
I understand this, but there has been no change with us and I am the administrator of JIRA and TMetrics, and I still have the same email. The problem occurred yesterday afternoon, and it is not clear why. Until then transferred times.
And asking for a similar error: How are the times back updated?
This error occurs when different logins are used for installing the add-on on the JIRA side and enabling time sync on the TMetric side.
It's not quite obvious, so let me explain. Add-on uses impersonation to log work time to JIRA on behalf of different users. On TMetric side, the user who enabled the synchronization is supposed to be the one who interacts with the add-on.
If users' logins don't match (we match them by email), the synchronization won't work properly. We won't have sufficient privileges to use impersonation.
That why we raise such an error.