The scheduler v5.0 will generate duplicate task at JIRA Software 7.3.4.

[致均(Harry) 盧]

As the title,we was downgrade the scheduler now,you can see the difference between and please fix it,thank you!

[Łukasz Modzelewski]

Hi Harry,

Thank you for reporting this.

Please give us some more details, that we could reproduce it:

• what is your database type ?

• have you been using earlier 3.x generation (for JIRA < 7.0) of the scheduler or did you started with 4.x

• what is the difference between that duplicated task with number '203' and the next one with number '305' ?

• what is the type of the issue, is it regular issue type or sub-task issue type ?

• did this occured on all projects or just in this one ?

The most important: please send us atlassian-jira.log file at [e-mail] so that we could analysie it.

Here is link to the documentation how to find log: https://confluence.atlassian.com/adminjiraserver073/logging-and-profiling-861253813.html

Best regards,

Łukasz Modzelewski

[致均(Harry) 盧]

Hi Team,

1.MySQL 2.Yeah,our JIRA upgrade from 6.4.13. 3.The duplicate issue totally same with original issue.Just have a different URL,which will give a separate ID. 4.Those are regular issue type. 5.All project,but some project didn't affect,which only have a little scheduler issue.

Best regards, Harry

[致均(Harry) 盧]

It have any update?

[Łukasz Modzelewski]

Hi Harry,

Please update to latest version 5.0.2 and let us know if this helped.

If not then please send us atlassian-jira.log file at [e-mail] so that we could analyse it (we didn't receive it, yet)

Or you can create a support zip file:

https://confluence.atlassian.com/support/create-a-support-zip-790796819.html

Best regards,

Łukasz

[致均(Harry) 盧]

Hi Łukasz,

We test this issue on 5.0.3 but the problem still existing.

Should I open other ticket?Or just keep tracing this ticket?

[Łukasz Modzelewski]

Please update to version 5.0.9 and check if issue still exists.

If it does please create new ticket.

Cheers,

Łukasz