Comments
-
Hello, You could create a group for these users and filter users by this group in this JQL query: assignee in membersOf("your group")
-
@Gulnoza Davlatova in what interface of Jira these users can not see the mentioned project?
-
Hello, I can answer the first question. You should take a backup of you server instance and restore it to cloud. Accounts and Teams from Tempo will not be migrated to Cloud. You should migrate Accounts and Teams manually
-
Ok. In what interface this project is not visible? Also try to use permission helper to check if a user have permissions for an issue in this project. You can find permission helper in System -> Permission helper.
-
Hello, Look at the project permission scheme and make sure that the required developers and users are granted the Browse Issues permission.
-
It is not available for a classic project. You need to create a next-gen project.
-
Hello, It is not possible out of the box.
-
Usually you include this user to the jira-service-desk group
-
Hello, Right now these features are not available, but next-gen projects are constantly getting new features. I hope in the future we will have the reports , you need.
-
Hello, It means that you have a classic project. The Roadmap feature is not available for classic projects. You should create a next-gen project and enable this feature.
-
You would need a scripting add-on for it.
-
These are not global permissions. These are project permissions. Kindly read the link I provided. You should open System->Global permissions
-
It is the next-gen project template. You can not release issues there. All issues in the most right column will disappear after 14 days. You can not change this behaviour. Only if you switch to the scrum board. Go to project settings -> features and enable the Sprints feature.
-
You are welcome!
-
What do you mean you saw one of the histories of the change? Do you mean you could not see all history changes?
-
I do not understand what you mean by "write a query with JQL"? If you mean to write an inner query like in SQL, then it is not possible. For example, select (select fielda from table2 b where b.id = a.id) from table1 a It is not possible in JQL
-
If a user is in the Service Desk Team, it does not mean that this user is an Agent. You should go to User Management find this user and have a look if this user has the Service Desk Application access.
-
What do you mean to write a query within JQL?
-
Hello, if you want to use the out of the box JQL, then you should use the linkedIssue function. The problem is that you need to provide an issue key as the first parameter, that is why it is not that much flexible. If you want to have a more flexible solution, you would need an add-on. For example, you could use the Power…
-
If you are on Cloud, then there is no upload add-on button. Here is how you install an add-on for Cloud: https://confluence.atlassian.com/confcloud/managing-add-ons-or-plugins-724766519.html
-
Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a JQL query like this: 1. project = xx and issuetype = feature and status in ( On Deck, Backlog, Open)…
-
You should apply the issue security scheme. You can not limit visibility of issues from the same project in a board by other means.
-
Hello, That is right you have to setup Issue Security Schemes. it will have effect on boards and filters. User will see only issues, which they are supposed to see by the issue security level.
-
Hello, Next-gen projects do not have the same functionality as classic project. Select lists are not there yet, but they are on the roadmap for next-gen projects.
-
Hello, That is right. If you create a project with shared configuration, a classic project is created.
-
I have never configured bitbucket as a maven repository because it is not created for it. I think we should use the right tools for each thing.
-
1. Create four filters: https://confluence.atlassian.com/jiracorecloud/saving-your-search-as-a-filter-765593721.html 2. Assign these filter to the four boards (board settings -> general): https://confluence.atlassian.com/jirasoftwarecloud/configuring-a-board-764477974.html 3. Share each filter with a certain group or a…
-
You are welcome!
-
I am not sure about it. I am a Jira user like you :)
-
Not for new project but for next-gen projects. It is a different type of projects.