When the users work in different projects with sprint planning to track the status of the projects, the user finds it very difficult to find the status of each project, because of the dependency of the project.
When users are trying to configure the projects, the dependencies between the projects are not automatically tracked and noted in the base software.
When users are trying to manage projects with their requirements, they are not able to use the Jira effectively because Jira provides a vast array of features that are not required for their project.
When the users are trying to make some changes and try to save the confluence changes if the other user also makes the changes in confluence, you have to save the other user changes also and while viewing the confluence, if you want to edit, the user will be redirected to other pages.
When the users are adding the issue, it is not appearing in the timeline and some of the issues depend on each other to complete and the issues are missing the estimation budget fields.
When the user tries to find the current status of the project, it is very difficult for the users to know about the status of the project with different views.
When the user tries to search for the particular issue, the search result will load after taking some time and the search result is not sorted or ordered based on any fields and the completed issues will be shown in the search result.
When the user tries to use the releases to separate the issue in different versions according to the priority and want to delete the issues after completing the first version issues, the user finds it very difficult to manage the issue on particular version and there is not an easy user interface to explain the flow of the releases.
When the users try to configure the organizations, the user interface asks the users to enter the schema for the organization and give value to the additional fields to configure organization and the users find very difficulty in handling the project with the organization in Jira.
When the user changes the resolution of the issue and tries to revert the resolution of the issue, the user finds it very difficult to revert the resolution of the issue.
When the user tries to assign members or change priority with search, the auto-filled list is not displayed correctly and the dropdowns for assign members and priority are not user-friendly.
When the user tries to create the issue, the user is not able to edit the type of issue as a Story, Epic, Bug Item, or a Task and it’s by default, the issues will be randomly chosen by Jira itself.
When the user tries to convert one or more already existing tasks, the user is unable to find the option for performing the bulk action and it is very difficult to convert more than one task into subtask of another task without an easy user interface.
When the user tries to filter the board with particular version and if the particular task has subtasks and the task is only assigned with version and in the filtered board, the task is only shown without subtask and the warning message should be shown while adding the version to the task with subtask about the filter.
When the user tries to create an issue with the version filtered view, after creating the issue, the issue is not visible in the filtered view and the user find it very difficult to add the version to the issue.
When the user tries to create an issue after creating an issue, the create issue button is hidden in the board.
When the user tries to convert an already existing task into subtask of another task, the conversion of the task into subtask of another task is very difficult.
When the user tries to add another version after adding one version, the create version button is disabled and it is very difficult to add more than one version without an easy user interface.
When the user tries to add more than a task with defined version and priority, the add task form is not allowing the user to select the template for pre-filling the details in the added task from.
When the user performs any action in the issue, the user receives the mail notification for every action and the users are not able to change the email notification period in Jira.
When the user wants to see the other user actions in the app notification, the notification section is very difficult to access and it is not user-friendly.
When the user has a couple of pages in the sidebar, a scrollbar will be displayed between the pages and the option to expand/collapse the sidebar and the scrollbar is very difficult to use regarding the scrollbar width.
When the user tries to set up Jira, it takes a huge amount of time to set up and configure and the setup is not user-friendly.
When the user tries to open the project or create a list of issues and edit issues, the page is loaded for every action taken by the user.
When users need features from Jira they request plugins, which contributes to UI complexity.
When the user tries to use the Jira for the first time, they need to fully understand the agile management process to fully utilize the options in Jira.
When the user tries to access Jira with assistive technology, the users are not able to easily access the Jira.
When the user tries to use Jira for the hardware development projects, there’s not a lot of flexibility in JIRA for their workflow.
Say, you've been pair programming or working in a group for a particular task. In Jira, assigning a task to multiple people is not possible.
In Jira, we cannot change the default assignee in projects from the administration console. Assignable users are defined in the permission scheme. But, Jira does not allow us to modify the default assignee. It is defined as the Project Lead by the system.
In Jira, search is extremely buggy and everyone needs to figure out their own way of searching the tasks. For example, if a task has '[fe]', if we search 'fe]', it will return that task. But, if we search the exact '[fe]', it won't return that result.