Cannot move a card to a column despite workflows and transitions being configured

[Deleted user]

Greetings, 

I'm having an issue where I cannot drag a card to a new column I recently made. 

I want to move a card from "Ready to Deploy" to "Inform Stakeholder". The workflow transition is set up to allow this. The diagram indicates the transition is there. But when moving the card, the column does not display the Inform Stakeholder column as availble as available. 

This workflow transition is configured: 

Yet here is what is shown when trying to drop the "Add Hearken Newsletter to Subscriber page" ticket from Ready to Deploy to Inform Stakeholder: 

Any suggestions for what might be blocking this move? 

Thank you for any insight you may have to share. 

[amanbajwa]

Update the "epic name" in the epic.

[pborkowski]

Hi,

This really sounds strange, I'd like to look into it more carefully. Could you be so kind and provide a sample of your import file here or via JIM Project (https://ecosystem.atlassian.net/browse/JIM) and share your JIRA/JIRA Agile version number? I'm having difficulties with reproducing this problem on my local JIRA.

By the way, please note that CSV Importer is sorting the input file before executing - it's always creating epics first. It's necessary for JIRA Agile to be able to correctly link issues during import. So if you have Epic in the middle of your file it will be pulled up.

[DI2E Licensing]

origin-Don't Map,id SORT BY,Issue-Key,status,Date Modified,description,reporter,priority,Date Created,component,Stage,summary,milestone,assignee,issue type,sprint,resolution,Epic Link,EPIC - don't map,story points,label,label,label,label,label,label
epics,1,VAPAAAA-1,,,1 a description,you,,,,,EPIC 1: INGEST,,me,Epic,,,,,,,,,,,
epics,2,VAPAAAA-2,,,2 a description,you,,,,,EPIC 2: LIST,,me,Epic,,,,,,,,,,,
epics,3,VAPAAAA-3,,,3 a description,you,,,,,EPIC 3: MAP,,me,Epic,,,,,,,,,,,
epics,10,VAPAAAA-10,,,10 a description,you,,,,,EPIC 10: TRACKER,,me,Epic,,,,,,,,,,,
backlog,266,VAPAAAA-266,new,2013-06-11 16:32:47.884688+00:00,266 a description,you,,2013-03-25 18:41:36+00:00,,,266replaced Summary,,me,User Story,,,VAPAAAA-10,EPIC 10: TRACKER,,Tracker,,,,,
backlog,268,VAPAAAA-268,new,2014-01-08 20:14:18.517253+00:00,268 a description,you,Medium,2013-03-25 18:45:02+00:00,,,268replaced Summary,,me,User Story,,,VAPAAAA-3,EPIC 3: MAP,1,Tracker,,,,,

Sample above. thanks!

[Matt Brown]

Hi, was there ever any resolution to this?  I'm seeing the same problem, here's my CSV (the

Type,Priority,Component,Epic Name,Epic Link,Summary,Description

Story,Major,Austin,This is my epic name,SPEC-3402,Bulk Import Test,Test test

[Matt Brown]

Hi all,

I'm going to reply with the resolution in case others run into this.  The problem isn't with the CSV import at all.  The problem is the Epic itself does not have an "Epic Name" in it, hence the "unlabeled-..." epic label in the backlog.

Matt.