-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.2.8, 7.7.0, 7.6.3
-
7.02
-
10
-
Severity 3 - Minor
-
0
-
If you use have a Workflow Scheme that uses the jira workflow for all/some Issue Types, you are not able to drag and drop issues in a Sprint.
Steps to reproduce
- Create a new Workflow Scheme and associate all issue types with the jira workflow.
- Associate this new scheme to your project.
- Go to the Scrum Board and try to drag and drop issues.
You will also notice that if you navigate to Board Configuration and try to map the statuses, they will be there with the following warning in the HTML tooltip: This status is not available in any of the workflows used by this board. To remove, drag it to unmapped statuses where it will no longer be available.
Note that this will only be displayed if the jira workflow is the only associated on that scheme. If you have more than one workflow, then no warning will be displayed and only issues that are using the jira workflow will work.
Expected results
Jira should allow you to use that workflow, especially since when copying that workflow and not making any changes, it works just fine.
Actual Results
When using the jira workflow, you are not able to drag and drop issues from one status to another in an active sprint.
Additional information
This could be related to the fact that the jira workflow is hardcoded to the system and does not show in the jiraworkflows table, so it is possible that the code is looking for an existing workflow and not finding one.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-16445] Drag and drop in an Active Sprint does not work when using the jira workflow
My backlog is currently not able to perform the drag and drop function
Hi there,
my customer does not have the the capture plugin for JIRA. But we do face the described issue and are not able to drag&drop issues that use the default Jira workflow. We are on Jira 7.9 at the moment.
We could workaround the issue by copying the jira workflow and assigning this exact copy of the workflow to the workflow scheme used by the affected project. However, what is the issue with the default jira workflow?
Update: We have identified that after copying the workflow as described above, the workflow scheme can be changed back to include the default Jira workflow and the drag&drop still works. At least for now...
An update by the vendor has just been released to fix the issue (confirmed it works):
https://marketplace.atlassian.com/apps/306183/capture-for-jira?hosting=server&tab=versions
Version 2.10.2.210200067 • Jira Server 8.0.0 - 8.2.1 • Released 2019-06-12
Summary
Jira 8.x Compatibility Release
Details
Jira 8.2.1 compatibility release
Fixed Unable to drag and drop issues from one work flow status to other status in Active Sprint
Also fixed the issue for me!
Do share a link to watch for an issue with the vendor of Capture plugin if anyone finds one.
There is a KB article describing the problem here:
... but no solution other than to disable the plugin.
@Scott Heckel! Thank you very much!!!! Thats solve the problem! Cheers Tamas
Disabling Capture for Jira and refreshing the page worked for me. Thanks @Nasser. Is there a separate bug we can watch for that issue?
Not sure if this is related to you guys, but today we faced similar issue. After upgrading to 8.1.1, drag and drop for subtasks on boards stopped working. It was strange, if we created a brand new board, it would work for a couple of times and then stop working. After some googling we found this ticket:
Sure we used Capture for Jira plugin. We immediately disabled that plugin and after that it all worked for us.
Hope this helps.
Using Jira Core 8.2.1 and drag and drop functionality is broken on Chrome and Firefox.
No console errors or warnings.
Drag and Drop within Kanban Board just does not work. Also enabled Chrome Touch API flag.
https://vimeo.com/339546371/64ba7a49c9
What can I do to get drag and drop working again?
No permissions changed. Just fresh update to 8.2.1.
We were affected on a Kanban board that only had tasks with the default Jira workflow. Jira 8.3.3
Using a copy of the workflow solved it.