All ideas

Thank you for providing Japanese translation on JIRA screen. I request to have both Japanese translation and original English on JIRA screen. At this moment, we need to verify the accuracy of Japanese translation in order to use in real project. W...

Would like to see an audit trail or edit history of a workspace that shows everyone's actions (deletions, adding tasks, etc) so it's easier to know what changed. Would also want to be able to recover deleted work items in case someone accidentally...

Context/ask: Would it be possible to set up Concourse access for a group (e.g. "ECR Team")? In other words, when we notify engagement leaders/teams of an ECR, we could simply ask them to add "ECR Team" for access to their Concourse workspace, and ...

Put Simply: This proposal suggests adding an AI feature to JIRA that automatically checks designated SharePoint folders to assess task progress and update ticket statuses and comments accordingly. The goal is to reduce manual workload for users an...

Put Simply: I propose adding a Conversational AI feature to JIRA that enables users to manage task progress through natural dialogue. This aims to reduce the operational burden on users by automating status updates, comments, and logs based on AI-...

We would like to have an AI tool that can automatically create JIRA tickets (Work Items) based on meeting minutes and other project-related documents.

Put Simply: Regarding document creation tools using Gen AI, I would like the AI to automatically update the TSD (Technical Specification Document) when the FSD (Functional Specification Document) is revised through discussions with the client afte...

Please remove sub-offerings that don't have content or mark as "coming soon" in their name so that people don't click on them to check if there's quality content inside

There should be a way for people to get to Concourse PDM workspace from their SharePoint (SaveIt) as well as access Jira from SharePoint and other way around. Right now we are left guessing if an engagement has workspace and, if yes, which is it.

Currently, CSV bulk import in JIRA only supports creating new work items. If task updates could be performed by overwriting existing work items using key fields via CSV bulk import, it would allow users to easily modify multiple work items at once...