Sync of Issue with subtasks doesn't always work

[Joachim Seibert]

Our customer Allplan uses your plugin to Sync the fixVersion field between a User Story and its subtasks. Attached you will find screenshots with the sync configuration, the change history of the user-story (long list) and the change history of the subtask (short list). There you will see, that only the changes from 07/Jan/19 and from today (06/Feb/19) were synced. (nothing to be found in the error list of the listener)

Do you have any idea, why some of the changes were lost?

[Yury Oboz]

Hi.

What version of JIRA and version of Add-on is used?

Changes 28/jan/19 17:08 made is mannualy?

[Yury Oboz]

Anja Neumann have permission to change fix version in destination issue?

[Joachim Seibert]

Yes, Anja Neumann of course has write permissions as AIDP-35195 is a subtask of AIDP-35193 and permissions of subtasks are granted by the permissions of the parent issue (which is the one she changed obviously).

Version of Sync fields: 7.5.3 Version of Jira: 7.9.2

[Joachim Seibert]

And concerning your suggestion with the permission: If you look at the 2 screens, you will notice, that one of the changes Hans Schmidt made today was not synced either.

[Yury Oboz]

Have AIDP-35193 a one subtask or more?

[Yury Oboz]

Can you enable logging for addon like this: Go to Admin -> Logging and profiling -> Configure logging level for another package. -> type "ru.slie.jira.fsync" and Logging level = DEBUG

[Joachim Seibert]

The UserStory has 3 subtasks: AIDP-35194, AIDP-35195, AIDP-35196. But all subtasks have the same history - none of them has done the fixversion Update auf Anja Heumann for example. Logging is enabled. Should we just wait now and collect some data until a certain point or should I perform any specific action to enforce a possible error?

[Yury Oboz]

What is type of field "Team"?

I'm trying to reproduce the error, but so far without result

[Joachim Seibert]

"Team" is a select list. Do you suppose, that it has something todo with the specific configuration in this case? I thought it must be more a sporadic / temporary problem.

[Yury Oboz]

I do not know why the problem occurs, so I try to gather more information.

If Error tab is empty, then no error on udating issue. Maybe JIRA can't fire event on updating issue or have bug on save change history.

P.S.: Maybe somebody deactivated and then activate listener)) P.S.: Were there the same problems with logging enabled?

[Joachim Seibert]

Ok, we are waiting for such an error again, so I can extract the (debugging) log file entries and can send them to you.