Unable to Create Subtasks - "Cannot read property 'key' of undefined"
I'm unable to create subtasks for ANY scheduled issues. Each time I try it returns the error "Cannot read property 'key' of undefined."
Screenshot attached along with debug / error line details. Please fix ASAP! I can't even evaluate this product because it doesn't work. Also, if you can please extend my trial that would be great considering I haven't been able to even test the product due to this!
Comments (11)
-
-
- changed status to open
-
-
assigned issue to
-
assigned issue to
-
reporter Ah interesting. I think I had one JIRA issue in the project before creating a scheduled issue, but I can't confirm. The issue also since went away on that project.
Based on your comment, I tried creating a new project and then with no existing issues, created a Scheduled issue. Next, I tried to create one subtask for that issue and indeed I replicated the result of "Cannot read property 'key' of undefined." I think you are right that it's based on a project with no existing issues.
-
- changed status to resolved
-
reporter Why is this marked as resolved? I still see the issue in my instance.
-
- changed status to open
Dear Shawn,
I'm sorry for hurrying too much with resolving it. In fact I was asked to close it. The ticket will be reopened and I'll ask my colleagues to take a closer look at Your case.
Sorry for the inconvenience. Dominik
-
Shawn,
We've discussed the issue. To assist properly, I'd like to obtain an information if you have already created an issue that is not an "epic" nor of a sub-task type - if you have created any of those, then Scheduler CLoud is not going to work properly.
If possible please provide me with screenshots of the created issue type(s) in a project where this problem occurs.
Many thanks, Dominik
-
reporter Hi, Yes, the problem only occurs when there are no prior existing "jira issues" for the project. I think this is a problem that should be fixed though as it provides a poor user experience. Thanks, Shawn
-
- changed status to resolved
Dear Shawn,
Please be advised - fix resolving the problem of yours is to be released in this week.
Many thanks, Dominik
-
reporter thanks for the update
Thanks, Shawn Souto Owner / Founder shawns@designbyssi.com
- Log in to comment
Dear Shawn,
I'd like to confirm whether the instance you tried to do the above mentioned steps is a fresh one?
The reported case was tested by one of the developers from my Team and it seems that if one creates a new instance, to have a Scheduler Cloud working properly, there's a need to create an issue that is not a sub-task one, so the add-on can have a proper point of refence and match appropriate key. I'd like you to check if non-sub task issue was created first.
Many thanks, Dominik