Power BI Authentication Error for OData Feed connector

[Don S. Thompson]

Trying to connect to Jira with Power bi using the OData Feed and the Access Token. I get the Couldn't Authenticate error.  Entered my User Name (I have admin access), the token was entered in the password, and the URL created by the Power Bi connector screen (Documented here: https://aserve.atlassian.net/wiki/spaces/PBCFJC/pages/2729377793/How+to+connect+to+Microsoft+Power+BI+using+Access+Token)

I presume there is no way to see exactly what failed, the URL, the user ID, the token, so I am limited to asking, what credentials the account specified under User Name should have. What permissions, where should it be created in Jira, etc.

Need more information than, "didn't work", if you know what I mean.

Thx

[Nic Brough -Adaptavist-]

Not really, most Cloud users go to Confluence for questions, it's more natural in a system built for sharing generalised information rather than task-tracking.

[Esther Strom]

Well, yes, if it's generalized information you're looking to share, and if you're using Jira only for "task tracking".

I work for a software dev company, and we use Jira as a complete Agile planning system - our tickets are not simple tasks; they can be epics, stories, and defects.

We're looking for a way to deal with questions and answers asked in the process or working with a specific ticket in Jira - i.e. someone assigns me a story to add specific functionality to my client's website. Right now, we communicate internally with developers, QA, product owners, customer support, project managers, and business analysts. That can result in a huge, messy comment chain that people have to search through to find information.

We'd like a way for a developer, for example, to ask a specific list of discrete questions about the ticket and requirements, and be able to track whether those questions have been answered, and for it to be easy for other users to find questions and answers, rather than having to read through 30 or 40 comments. (We have a distributed workforce, so saying, "just talk to people" doesn't work; even if it did, these kinds of questions and answers need to be documented for future reference.)

Telling people that if they want this functionality, they need to create a Confluence page for every ticket that has questions is just asking to be burned at the stake. And it's ridiculous that you'd have to. It seems like this should be pretty basic functionality in a ticketing system.

[Nic Brough -Adaptavist-]

Oh gods, that's massively overcomplicating what an issue tracker is for.  For the vast majority of people, the comments should be more than enough.  When you're throwing vast amounts of conversations into an issue like that, it's time to put it in a proper documentation system, not some untracked threads.  (Midway between "easy to use issue tracker" and "document it properly" there's lots of room to do the questions as sub-tasks though)