Copy Workflow issue

[Chad Brooker]

Hello! 

New JIRA admin here. We had a software engineering workflow that we needed to add a zendesk integration in as a post function. So as to not mess with other projects. We copied the workflow scheme and workflow and added the integration, so that everything else should be the same. Unfortunately, After we made the change, we couldn't submit a ticket using that issue type. I checked every screen and screen scheme and everything was the same as before. When I switched back to the original workflow for the issue type. We were able to submit the ticket. The issue creation view did seem different, but I did not put in any different information.

Is there something that I am issing?

[Nic Brough -Adaptavist-]

All of them.  Atlassian do not put "unstable" releases into the download list (they do release "early access", which you could call "unstable", but these are held separately).

I would tend not to go for a release with a .0 on the end because these are new to market and Atlassian can't test every possible combination that's out there, so the .0 releases may have some issues with some specific hardware/os/config setup.

But the answer to what's "stable" is "any version you can download".

There is also the Enterprise release, currently 7.6.latest, which will be supported and patched for a much longer time than other versions.e

[Surender Reddy]

All good with the answer but why would we prefer 7.6 when we have 7.12.3 in the market with lot new features . is there any problems or issues if we upgrade to latest version 7.12.3 . can you please let me know .

[Nic Brough -Adaptavist-]

Because 7.6 is the enterprise release, so it's going to get updates at that version for a long time.  If you encounter problems in 7.12.3, and Atlassian fix them, they will go into 7.12.4 or later and you'll need to upgrade to get them.

[Surender Reddy]

thank you for the information