Incompatibility with plugins
Hi Wladimir,
Finally I found the root cause.
If plugins are using same class name for configuration, one plugin overrides the other and cause problems.
I raised a ticket to Atlassian about the topic.
However, I will not wait for Atlassian's solution, I will soon release a new Time to SLA plugin version fixing this problem.
Regards
Tuncay Senturk
TTS v3.3.3 has a bug fix for this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
tuncaysenturk commented on issue #30: | |
Incompatibility with other plugin | |
Hi, Thanks for keeping me notified about the process. I am using JIRA API, and I am using it the right way. I really could not figure out the solution of this problem, and I need Atlassian developers' help on this issue. They should say something about this. Since I do not have permission, could you or your customer please add this comment to the ticket. Best regards |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Plugins are from different vendors, and both are compatible with version 6.2. As you can see on the support site for TTS other customers have reported similar problems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Could you check that you are using compatible versions of both add-ons?
https://marketplace.atlassian.com/plugins/com.iamhuy.jira.plugin.issue-alternative-assignee/versions
https://marketplace.atlassian.com/plugins/plugin.tts/versions
-- Pedro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.