You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
I administerd jira server for 8 years and now I am facing the migration to jira cloud. First of all I activate my free trial product. Now I am exploring the new platform and evaluating the first changes I have to set in my new platform in order to mainain some of principal settings of our old organization.
So I noticed that if I go in issue type I see only "Epic" and not the others type such as Task or Bug. And if I go in user roles (secure/project/ViewProjectRoles.jspa) I see only Administrator and not developers or user. Why I can't see the default values of the platform?
Am I looking in the wrong place?
Please help me!
The cloud platform has (a lot of) templates available to create projects. Once you create your first project(s), you will see these default configuration items appear.
Also, when you migrate from server to cloud, your server configuration will be migrated over as well.
Since you seem to have a long experience with server - even though it is not really what you are asking for - I would recommend you to have a look at the difference between company managed and team managed projects. Company managed projects are configured very much as on server, but team managed projects are unique to cloud and have a very different configuration approach. You may want to check out this support article to learn more.
Hope this helps!
Hi Walter,
thank you for your answer. When I started my jira cloud version I create a brand new projcet "Test" (what a fantasy!) and I see that the issue type related on these project (chose from a jira template) are epic, task and subtask, but if I go in /jira/settings/issues/issue-types I see only "Epic", I expected to find also task (and subtask in subissues).
So...why?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Most likely because that template was team managed? Issue types from team managed projects are not shared. When you open your project, check the bottom left corner of your screen. You should be able to see if your project is team/company managed right there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Walter,
Surely I need to study the new platform and I thank you for your explanation. But I think that this kind of decision.
Immagine that someone brand new of Jira stars to administer the platform and, don't seen the issue type "bug" create this to use on a brand new project. After that the new administrator create a new guided project team managed that use the issue type bug itself. What will be the platoform behavior? Will you have two different type of issues named in the same way?
Thank you so much for spend the time for me, I now that for the cloud platform I am a beginner.
Chiara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.