I am trying to upload a workflow to the Marketplace. I have uploaded workflow to the Marketplace twice before, but never had this issue.
So I upload the JWB file and followed all steps. After the last step, I am shown the first screen that has an error that Addon Key is Required. What's interesting is that the field is disabled, so even if I know the addon key (which I don't know), I won't be able to enter that in the field.
Any suggestions/recommendations would be appreciated.
There has been a strikingly similar previous issue Create add-on form doesn't show plugin key field for shared workflow (AMKT-10420) about a year ago:
When creating a new add-on listing for a shared workflow (.jwb) file, after you upload the file, all the usual fields become visible on the form except for the plugin key. It is inappropriately showing the "key is not editable because it comes from the plugin artifact" state, as it would for a regular plugin jar, even though a shared workflow has no plugin key in it. It should be showing an editable field, as it would if you selected "my add-on is not directly installable."
Accordingly, this seems to be caused by a respective regression in the Marketplace code base (or a deliberate, yet incomplete related change) - if no Marketplace team member chimes in here directly, your best bet is probably to just add a new issue referring to the former one in turn.
The security level of AMKT-10420 is listed as Public - (Visible to anyone, including anonymous viewers.), and it can indeed be browsed when linked directly, yet this doesn't seem to be the whole story, insofar the JIRA issue macro yields an exception when this answer is viewed anonymously:
I have created https://ecosystem.atlassian.net/browse/AMKT-13277 to track this oddity in turn.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG