microsoft / azure-pipelines-jira

Azure Pipelines for Jira
MIT License
15 stars 6 forks source link

Can't see the "Releases" field in Jira tasks #35

Open yohanb opened 4 years ago

yohanb commented 4 years ago

Hi, I'm getting the same error reported in #15 . I looked at the available issue fields in the configuration and it isn't there. image

I also took the time to uninstall/reinstall the jira app and Azure DevOps service connection. Can you please help me out? Thanks.

steenole commented 4 years ago

This could very well be the same problem, that I have encountered. The problems is in JIRA. Please read the comments on these two issues:

https://jira.atlassian.com/browse/JRACLOUD-73330

https://community.atlassian.com/t5/Jira-Software-questions/Releases-panel-in-old-issue-view/qaq-p/1198728?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#M78040

yohanb commented 4 years ago

yeah @steenole, seems to be the same problem! Thanks for the info. Hopefully this gets some attention because it basically makes the extension unusable.

steenole commented 4 years ago

@yohanb Please leave some comments and votes on the JIRA issues. The more of that, the more hope for some attention, I guess...

yohanb commented 4 years ago

@steenole done and done. 🤞

yohanb commented 4 years ago

Maybe someone in the dev team (@shashban) can escalate this with Atlassian? It really kills the value for the integration with Azure DevOps.

yohanb commented 4 years ago

I guess the intern working on this integration is gone.... 😂 No love is given! :(

shashban commented 4 years ago

Hello folks ... As an owner for the integration, I must tender an apology here for not looking enough into the the issues here. We are working on a fix for the issue reported on the Atlassian marketplace (something went wrong) during the installation of the app. Can I request one of you to report the second issue on https://developercommunity.visualstudio.com/content/problem/post.html?space=21 Thanks

steenole commented 4 years ago

@shashban I appreciate the good intentions, but there is probably not much you can do, since the bug is in Jira (see my first comment). But if you have some contacts in Atlassian you can bring this up with, that would be highly appreciated. Apparently they do not find this bug worth fixing. 😒