Comments
-
Hello, I believe that your version is archived. To remove an archived version, you need first to unarchive this version, remove it from the issue and then archive it back. You can unarchive a version in Project settings -> Versions.
-
Hello, If you change the filter, it will not delete the ranking as long as you do not add the order by clause to your JQL filter. And even if you add the order by clause, you can always remove the order by clause and use the global ranking.
-
Hello, How do you get this message? A screenshot would help.
-
Hello, It means that either workflow or field configuration or screen configuration is not the same for bugs and tasks anymore.
-
Your understanding is correct. You should switch to the old issue view:
-
Hello, It does not matter which roles are created by default. You can always delete or add new roles.
-
Hello, You can restrict comment visibility in the old issue view: https://confluence.atlassian.com/jirakb/add-restricted-comments-on-jira-962353957.html
-
Hello, It would be nice to see screenshots with issue status, board configuration and issue placement on the board. Because everything you describe looks correct. The issue should be in the Done column.
-
You can export only issues for this project: project = your project
-
Hello, Have a look at this KB: https://confluence.atlassian.com/jirakb/how-to-migrate-projects-from-one-jira-cloud-application-to-another-779160766.html
-
Hello, The only way to transfer only one project from Server to Cloud is: 1. Create the project with all configuration (manually) 2. Export all data to a csv file on Server and then import this file to Cloud.
-
Hello, What do you mean by sprint data? You mean issues, which are in this sprint? If so, export all issues in this sprint to a csv file (sprint = your sprint) and then import this csv file to your production Jira.
-
Hello, You need to load your resources either in vm or soy template. For vm it would be like this: $webResourceManager.requireResourcesForContext("pluginkey:jira-plugin-resources")
-
Hello, You would need to restrict comment visibility: https://confluence.atlassian.com/jirakb/add-restricted-comments-on-jira-962353957.html
-
Hello, I believe that you are the only one who has manage sprints permission for all projects in your Jira. The JQL query for your board is not restricted to projects, that is why to start or complete a sprint on the board, you need manage sprints permission for all projects.
-
Yes, it is for Jira applications.
-
Hello, Have a look at Backbone Issue or Exalate: https://marketplace.atlassian.com/apps/1213645/exalate-jira-issue-sync-more?hosting=cloud&tab=overview https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira?hosting=cloud&tab=overview
-
You can retrieve data from Jira server via jira-api, if you make your application as an app for Jira (your app must be installed into Jira).
-
Hello, jira-rest-java-client is dependency for using Jira Rest Api. Jira-api to use Jira Java API
-
Hello, You do not need a Jira Software or Jira SD license for a user, who only reads data. All you need is to grant a Jira Core license (or JSW or JSD license) and provide Browse Projects permission to the required projects.
-
Hello, I believe that by saying Jira Java Api you mean Jira Rest API. If so, you can find examples on Jira Service Desk Rest Api here: https://docs.atlassian.com/jira-servicedesk/REST/3.6.2/ Examples about Jira SD Java Api you can find here:…
-
Hello, Out of the box only Jira Administrator can manage groups. You can have a look at this plugin: https://marketplace.atlassian.com/apps/1215247/delegated-group-management-in-jira?hosting=server&tab=overview
-
Hello, Try to use api token instead of the password: https://confluence.atlassian.com/cloud/api-tokens-938839638.html
-
To make a board shared, you need to share the filter for the board (board settings -> General)
-
Hello, Have a look at this answer: https://community.atlassian.com/t5/Jira-questions/how-to-share-filter-in-jira/qaq-p/97252
-
Hello, If you can somehow catch the required event on AWS, then you can use Jira rest api to close an issue: https://docs.atlassian.com/software/jira/docs/api/REST/8.3.1/?_ga=2.187548072.1220234070.1563774429-1149622764.1547637396#api/2/issue-doTransition
-
Hello, You would need an app for it. For example, this one: https://marketplace.atlassian.com/apps/1211499/issue-history-collector?hosting=cloud&tab=overview
-
You can try. Kindly read this info: https://confluence.atlassian.com/adminjiraserver/restoring-a-project-from-backup-938847691.html Please, pay attention that it is not a trivial task to restore a project, it may require to perform some configuration in your destination Jira instance.
-
Hello, You can create a separate workflow for the Bug issue type and add the jira.permission.edit.group workflow property to each status: jira.permission.edit.group=tester-group You can find more info here: https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html
-
Hello, You will loose the history of all tickets. Also you need to create all sprints and versions, which you are going to import, before the import.