Currently, the REST API doesn't indiciate if the given custom field has been defined as read-only or not. Here's a sample field definition for a read-only field as returned from `/api/v1/products/{productId}` {"id": "7002184427275897244","key": "k...

Drag and drop initiatives on a roadmap

I am using the Aha! Confluence add-on to present product roadmaps internally within the company in lieu of providing the URLs to the roadmaps/presentations to prevent company employees from having to access Aha! I would like to be able to disable ...

Super helpful if could simply hover over something like 'Activities Board' and a quick defitition came up. Or at least there was an easier accessable glossary. It's not the most intuitive to find.

What is the challenge? I track many todos in My work but I am unable to work through them in priority order. I am only able to sort by due date, workspace, or record. I would like to be able to see my most important todos first, regardless of due ...

What is the challenge? When selecting cells within a table to edit its content, clicking on the cell moves the scroll bar up instead of selecting the content of the cell. Also, I cannot always see where the cursor is. It seems to disappear which i...

What is the challenge? I want to include a callout box in a numbered list, but I can't. It's either making the whole list a callout box or when copying a callout box it's just taking the sentence, but not the box What is the impact? I cannot use c...

Use Case: When an existing account holder of Aha! (Roadmaps and Develop), every time I add seats to include more Develop engineers on board, Aha! allows the addition but emails an invoice. Why can't the client choose the preference to pay Aha! in ...

Our organization often maps Master Features against Features as dependencies, and there is presently no way to do analytics on this data because the information is not available via API. Please expose.

If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's). However we are...