-
Bug
-
Resolution: Unresolved
-
Low
-
Minor
-
M
Issue Summary
When opening a dialog with
AP.jira.openCreateIssueDialog()
the old create issue dialog is used and not the new one. The new one has a cleaner interface as well as minimise/maximise buttons.
The old dialog displays markdown formatting vs wysiwyg editor in new experience. Resolution field is always required on old dialog vs new experience, in which there is no such problem.
Steps to Reproduce
- Create a Connect app that has code that calls openCreateIssueDialog() like
AP.jira.openCreateIssueDialog((data) => { document.getElementById('text').innerText = JSON.stringify(data) }, { fields: { summary: "Hello World" } }); }
- Activate the code (e.g. with a button click)
Expected Results
The new dialog opens
Actual Results
The old dialog opens
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
openCreateIssueDialog opens old issue create dialog
-
Bug
-
Resolution: Unresolved
-
Low
-
Minor
-
M
Issue Summary
When opening a dialog with
AP.jira.openCreateIssueDialog()
the old create issue dialog is used and not the new one. The new one has a cleaner interface as well as minimise/maximise buttons.
The old dialog displays markdown formatting vs wysiwyg editor in new experience. Resolution field is always required on old dialog vs new experience, in which there is no such problem.
Steps to Reproduce
- Create a Connect app that has code that calls openCreateIssueDialog() like
AP.jira.openCreateIssueDialog((data) => { document.getElementById('text').innerText = JSON.stringify(data) }, { fields: { summary: "Hello World" } }); }
- Activate the code (e.g. with a button click)
Expected Results
The new dialog opens
Actual Results
The old dialog opens
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.