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-]

The issue view takes the list of your fields and re-arranges them into a set of panels.  Dates and times get pulled out into a date panel, people and groups go into a panel, the system fields go into another, estimate and work-log another.  Description, links and subtasks all get their own panels.

Once it's pulled those out, the rest of your fields are placed in the custom fields panel.  That will include your "acceptance criteria".  But, of course Description and others have been pulled out elsewhere.

[Jack Hunter [HeroCoders]]

Hello @Eli Moshe,

As Nic explained you cannot control where the field is located precisely.

If Jira custom field or its location does not work as expected then you might consider third-party add-on.

My team created Issue Checklist app that solves the acceptance criteria and the definition of done problems through a list of check items. We also use it for testing notes and as a simple ToDo list so the number of possible use cases is very extensive. 

It is located on Jira issue page below Description as shown in the screenshot:

Issue Checklist allows blocking resolving the case if not all items/criteria are completed. It also allows to mention users, link issues, display checklist progress in various places (including issue cards on Agile boards), define a default checklist for a project or issue type and more.

I hope that helps.

Cheers,
Jack