You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Did anyone notice that Big Gannt plug-in changes Jira filed "start date" and "end date" automatically? it's affecting my dashboards and data.
moreover, I can't see who changed the end date with the history section of the issue.
I would love to hear your ideas on how to handle it.
I will try to shed some light on the application logic involved here.
Every change on Jira issues needs to be executed in the name of a user - it is a Jira requirement. The BigPicture/BigGantt changes Start/End dates automatically but these changes are triggered by actions executed by users working with the app. Some changes are directly executed and logged in Jira as done by the logged-in user other changes are queued and executed when the plugin can do it, for example when a user with the correct Jira permissions needed starts using the app.
The issue history updates in most cases are caused by re-synchronization that takes place when triggered by any of the following:
The above-mentioned actions trigger the re-synchronization according to the plugin logic that depends on the author and the changes introduced as well as the configuration of the plugin and are necessary to keep the data integrity.
Please note that:
If there were any changes made by a user in Jira, the events related to these changes are queued inside the app. The queue itself is being released every 5 seconds, so if there are a number of changes applied to the same issue within 5 seconds, the last person who updated the issue will be the author of the last queued change.
At the moment, our plugin does not store data that would allow us to precisely define a reason for task update. However, we are aware that tracking issue changes is important for our clients and the new functionality of tracking task time period via audit log is already on our Product Roadmap. More info here.
Should you need any further info regarding this, do not hesitate to ask.
Hi @Anna-BigPicture , we are having a related issue. I am the only person in our Jira environment at the moment, and the only person working on a project. I have one browser tab open, with the BigGantt view there. When I amend the start date of a task, whether from the column, from a pop-up window, or by dragging the bar on the gantt chart, it reverts a few seconds later. So if I change a start date to 30 November this year, for instance, a few seconds later it reverts to today's date (as the start of the project).
Any idea what might be going on here? Thanks!