Comments
-
You have Jira Cloud. It is not a next-gen project Jira. Jira Cloud contains both next-gen and classic projects.
-
I gave you the direction. I can not write code for you. That is the way it should be implemented.
-
Hello, If you want to prioritized tickets with drag and drop, you would need Jira Software together with Jira Service Desk.
-
Hello, If you finish a sprint with stories, which are not completed, those stories go to another sprint, but those stories still hold the finished sprint too.
-
Hello, You do not need a listener, you need to use either LifeCycleAware interface or InitializingBean interface. Here is an exmample: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Jira-plugin-quot-afterPropertiesSet-quot-and-quot-destroy-quot/qaq-p/97321
-
Hello, It is a filter created by a user in the Jira instance, where you are logged in.
-
You should add the Sprint field to the Create issue screen.
-
Hello, You can always make two subsequent calls. The first one to create an issue and then move this issue to a sprint. If you want to make it in one call, then set the Sprint field, when you create the issue.
-
Hello, Dashboards do not belong to projects. You can read this doc to find out how to create a dashboard: https://confluence.atlassian.com/jiracorecloud/configuring-dashboards-765593585.html
-
Hello, Dashboards do not belong to projects, that is why you can not create such a template. Reports are available for all projects from the beginning. That is why you can not accomplish your task even if you create a custom dashboard or report.
-
Hello, That is how my screen looks like when I create a project in Jira Cloud.
-
Hello, It is not possible on Jira Cloud. You will see all issue types for this project.
-
Hello, Reindex your Jira. System -> Indexing
-
You need to make a new installation into a separate folder and then change the port in the config.xml
-
Hello, You can use a query like this: sprint in openSprints()
-
Hello, The last time I migrated from Server to Cloud, Portfolio data were moved with a usual backup. Just try a test migration and you will see it.
-
Hello, What do you mean by unable to move? You do not have the To Do transition in the issue view? I would check the workflow for the story issue type (project settings -> Workflows)
-
Hello, If the developer fo the app has not developed this function (to limit the use of the app for users), then it is not possible.
-
It is strange. It worked for me on Cloud
-
Hello, It is not anonymous it is anyone.
-
Hello Steven, your solutions are valid for Server and the tag for the question is Jira Cloud.
-
Hello, You would need to develop your own program. Something like this: https://developer.atlassian.com/server/jira/platform/oauth/ It depends on your SSO provider. Or you could look for options in your SSO provider to let users use Rest Api with the Basic Authentication.
-
Hello, Go to project settings -> Features and enable the Estimation option.
-
Hello, You can not add the creator field to the people panel. Only the reporter field.
-
Hello, Have a look at the Structure app: https://marketplace.atlassian.com/apps/34717/structure-project-management-at-scale?hosting=cloud&tab=overview
-
Hello, Try to write like this: component = "name1" and component = "name2" and component = "name3" and so on.
-
Hello, I believe that you should use the Sub-Task Blocking Condition. Such validator does not exist.
-
Hello, You can not have a version for multiple projects out of the box.
-
I guess by project level dashboards, you mean reports. If so, then you can not prevent users to see the reports. But in these reports users only see data, for which they have browse permission
-
Hello, Make sure that the fixversion(s) is present on the Create issue screen for the Test issue type (project settings -> screens).