Closed andreasknoepfle closed 4 years ago
This is the errors that happen, just in case if it helps debugging this, which i don't believe :):
Should be fixed on master
now @andreasknoepfle. We just need a release, in case you have time (I'm quite busy with project work today) 😉
Somehow it still does not work so much with next-gen projects. The errors above disappeared, but still no ticket is found with version 3.2.0
Seems like we also have a problem with parsing the error we're getting for this scenario. That's what I get when debugging the extension:
Error: "Cannot parse given Error object"
parse error-stack-parser.js:35
fromError stacktrace.js:106
fromError stacktrace.js:105
Ie error-details.jsx:18
componentDidMount error-details.jsx:34
Wo React
unstable_runWithPriority scheduler.production.min.js:20
React 9
et render.jsx:31
onload popup.js:39
error-details.jsx:36:30
componentDidMount error-details.jsx:36
JIRA has a new type of project which we do not yet support fully:
https://confluence.atlassian.com/jirasoftwarecloud/working-with-next-gen-software-projects-945104895.html
An example is e.g. our own bchp board: https://bitcrowd.atlassian.net/jira/software/projects/BCHP/boards/7
Both views currently make tickety-tick error out: