Petter Gonçalves Atlassian Team

Hello Sadia, Actually, the most detailed way to restrict users in a project would be using the project permissions and not global permissions. That been said, there is no permission level to restrict users only to see reports on JIRA. They will need to have access to the issues/tasks to see their information in the…

Hello Kristina, You can configure a module in JIRA that allows your add-on to define custom global Permissions. Example: 1 2 3 4 5 6 7 8 910111213141516171819 { "modules": { "jiraGlobalPermissions": [ { "description": { "value": "Custom global permission for my add-on" }, "anonymousAllowed": false, "defaultGrants": [ "all"…

Hello Sorcha, JIRA Cloud already has a project template for Bug tracking where you can use filters to list your bugs. You can create it by: - Navigate to projects > Create new Project - Select to create a Classic project > Click change template: - Select bug tracking and create your project Let us know if there's anything…

Hello Stefan, answering your questions: 1 - Yes, you can select which security level should be the default one in the Project Settings > Security once you add a security Scheme to your project. the selected one will be added by default when you create an issue unless the user which is creating the issue have the permission…

Hello Julia, Thank you for your answer. Unfortunately, there's no way to sort an issue filter based on the time it was assigned since that's how your swimlanes are based. I'm afraid the only way to achieve the goal you need would be by changing your swimlane base to a parameter which can be ordered by the JQL filter, like…

Hello Brian, Yes, you are correct. In fact, you would need Administrator access to perform such operation, where you have access on both Classic and Next-gen projects.

Thank you for the feedback! We will be working on your issue in the ticket created by Andrew since performance issues need more details to be further investigated.

Hello Guillermo, Glad to know your issue is solved. I will absolutely take a look at your open request and let you know any insight I can give.

You are most welcome, Monika! Have a nice day. :)

Hello Ambica, Thank you for your detailed explanation. As mentioned before, User Picker fields can only be filled with a single user at a time where you can select any user from your JIRA instance. In fact, the User Picker custom field works just like the Assignee or the Reporter fields. Let me know if this information…

Hello Jocelyn, I'm glad to know you were able to find the root cause of the issue. Let me know if there's anything else I can help with.

Hello Jocelyn, That's is expected behavior. JIRA has one specific field to track each project type and a different field might not work: - On Classic projects, the estimation is measured on the Story Points field - On Next-gen projects, the estimation is measured on the Story Point Estimate field Using the wrong field, the…

Hello Raju, Unfortunately, JIRA does not have a JQL parameter to return all issues which have linked issues, but only specific linked issues from specific issue keys. This kind of query can only be achieved in JIRA Cloud by using a plugin, like JQL Search Extensions for JIRA. The mentioned plugin provides the…

Hello Guillermo, Can you please provide us a screenshot of the place you are trying to add the user? Indeed, we have some bugs informing this behavior on some user-picker fields: - Duplicate users returned if a user exists in more than 1 directory. - Duplicated users displayed as suggestion - Assignee picker shows…

Hello Katya, Unfortunately, there's no option in JIRA to select which options a single custom field will display for each project/issue type. The context of select list custom fields works in a straightforward way: Display all options or none of the options. That been said, it leaves us with two options: 1 - Use the…

Hello Monika, The views you provided are related to the New issue view and Old issue view designs. That been said, to change your New issue view back to the old one and vice versa in JIRA Cloud you can perform the steps below: - Click on your profile Picture > Personal Settings > Click to Turn-off or turn-on the New issue…

Hello Sean, Indeed, the default behavior of the backlog view (Including Swimlanes) of next-gen Epics is to return Epics based on their IDS, as mentioned in this feature request created to change this behavior: Currently, on Next-gen Projects, the list of Epics on the Backlog view are sorted based on their IDs. Meanwhile,…

Hello @Emanuella , Just like @elenushhh said, it's not possible to share custom fields between Next-gen projects and Classic projects. Each project template has its own set of custom fields. However, many other customers are also requiring this same feature, so we've created a feature request to our development team:…

You are welcome @Kylie Manning Thank you very much for your feedback. I'm glad to know you were able to achieve the functionality you needed. Have a nice week! :)

Hello Christian, Welcome to Atlassian Community. While JIRA has been developed primarily as an issue and project tracker out of the box, you can use JIRA for requirements management in conjunction with Confluence. Here's how Atlassian uses JIRA to performs it: Atlassian uses a public instance for our requirements…

Hello Jocelyn, Just to make sure we are on the same page, I would like to clarify the concepts of the Next-gen projects and New issue View since they are two different features: - The new issue view is only a new layout of JIRA software, which can be configured on Classic and Next-gen projects, however, can only be turned…

Hello Aaron, Unfortunately, JIRA does not have a JQL parameter to return all issues which have linked issues from a determined issue type, if I have properly understood your request. This kind of "sub-filter" where you will search for issues based in the fields of linked issues can only be achieved in JIRA Cloud by using a…

Hello Jessica, Welcome to Atlassian community! I understand that you would like to receive e-mail notifications on a determined time-frequency displaying a list of all recently created issues together with their summary. Is that correct? I believe you can use filter subscriptions to configure what you need. You just need…

Hello Aftab, There are some errors similar to the one you are informing when importing CSV files mapping next-gen custom fields, as you can see in the bug reported below: - CSV import will fail if Next-gen custom field is mapped Can you please confirm if you are importing a next-gen project? If that's not the case, can you…

Hello Roman, JIRA does not have an inbuilt field which would return the age of tickets, however, there are some plugins that you can use to achieve this goal. Basically, the steps to achieve your goal are: 1 - Use a plugin to create a calculated custom field which will receive the age of the issue (solved time - created…

Hello Adam, Welcome to Atlassian community! The problem you mentioned must be probably caused by misconfigured permissions. Is the user you mentioned the only one who is not appearing for you or is any other users also not displaying when you clicked in the field? I would check the following permissions: - Check if you…

Hello Janine, Unfortunately, the board estimation is not measured against Sub-tasks, but only again standard issue types. This is intended behavior for JIRA, due to the fact that the estimation in sub-tasks can cause confusion if you use it together with the estimation on Standard issues. That been said, we completely…

Hello Pawel, Unfortunately, it is not possible to create personalized filters that would be visible only for your users, however, you can use the parameter currentuser() in a filter to search for issues assigned to each user that is currently using the filter. Explaining better: - Let's suppose you would lie to create a…

Hello Katy, I understand that you would like to Sum all Story points from the issues which are configured with a specific label. Is that correct? Although JIRA does not have an inbuilt feature to perform this kind of configuration, there are two ways you can achieve this goal: 1 - Using the sumUp for Jira add-on, which…

Hello Stefan, Sorry for the late reply. Checking your drawing, I could understand the following goals: - You have two teams: Tom&Jerry and Garfield - JIRA Story Food together with all its sub-tasks and related tasks should be shared to the users in both projects, with both teams been able to access/edit the issues. - JIRA…