After Migrating to cloud / fields are not editable

[Arvind Swarnkar]

After Migrating from server to cloud / fields are not editable

where as on jira server its editable see here

[Ste Wright]

Hi @Arvind Swarnkar 

Those are two different tabs aren't they?

It doesn't look like the tab is there in Cloud - but that might mean it's the "general" tab.

In Cloud, the tabs work as follows...

• Tab 1: This is the "general" field tab - these fields are either on the left-hand side if paragraph/multi-line text fields, or on the right-hand side in a list if not.
• Tabs 2+: Still show as tabs in the issue view

Can you see fields like "Proposed Change To" and "Preparation Date" on the right-hand side?

See more information on how Cloud layouts work per Project here: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-layout/

Ste

[Arvind Swarnkar]

Thanks for your quick response

these are 5 tabs coming in jira server

But in cloud only 3 tabs, could you please help

 

arvind

[Ste Wright]

Hi @Arvind Swarnkar 

What does it show in the admin settings, against this Screen?

For example, were these tabs in separate issue operations in Server/DC, which might not be performing as expected in Cloud?

Ste

[GNarsimhagowda - Empyra]

Hi @Arvind Swarnkar ,

As @Walter Buggenhout  Suggested check for the relevant permission, If you have the needed permission.

Thanks.

[Arvind Swarnkar]

Hi @GNarsimhagowda - Empyra 

these are 5 tabs coming in jira server

But in cloud only 3 tabs, could you please help

 

arvind

[GNarsimhagowda - Empyra]

Hi @Arvind Swarnkar ,

Since you have migrated somethings will not correctly migrate over to cloud 

example the order of the fields on the screen,

So you have to manually create the tabs that are missing here.

Thanks.

[Walter Buggenhout]

Hi @Arvind Swarnkar,

Review your project permissions in cloud. It seems that you don't have edit issue permissions in your migrated project for some reason. Or also check if the field really isn't editable if you click into it. The UI in server and cloud are quite different as well.

Hope this helps! 

[Arvind Swarnkar]

How I can get edit permission in cloud ?

[Walter Buggenhout]

If this is a migrated project, exactly the same as on server, @Arvind Swarnkar . Your project will be company managed, so it has a permission scheme that you can find via Project settings > Permissions. In that permission scheme, you will see a list of all project permissions, edit issues being one of them.

If your project is set up properly, edit issues will be assigned to one or more project roles. In Project settings > People make sure that you are assigned to a role with that permission.

If you can't access project settings, that means you do not have the necessary admin permissions either. So, in that case reach out to either your organization's Jira admin or an administrator of your project to check this for you.

[Walter Buggenhout]

About the number of tabs you see, @Arvind Swarnkar go to project settings > screens in your project.

You should see the configuration there of the screens used in that project. I am not aware of limitations on the number of tabs displayed in cloud, but I do know that initially tabs didn't exist at all. If those tabs exist, you should see them in the screen configuration.

If those tabs are not there, you'll need to think of other ways to make those fields visible. You may have to reorganise your tabs or get rid of them entirely. Again, you may need help from an administrator to change the screen configuration.

Just on a side note: didn't you test this prior to migration? 

[Arvind Swarnkar]

Hi @Walter Buggenhout 

Thanks for your response

Please find this step during migration

How I can overcome with these plugins,

[Walter Buggenhout]

Hi @Arvind Swarnkar,

I hope you are still in the testing stage of your migration - if you already migrated in production, you may be facing a tough time fixing all these things now 😳

For the last one (SSO), Atlassian has its own solution in cloud, Atlassian Access. If you need Single Sign On in cloud, read up the documentation online and assess if you need it. It is a separate subscription that you need a license for and that has its own setup.

I am not familiar with the other two apps, but the message basically means that there is no automatic path to migrate those apps (and the features they provide) to cloud. As cloud and server are technically totally different platforms, certain features cannot be implemented in server the same way. Some apps simply don't exist on cloud or there may be different, often native ways to provide the same or similar functionality.

You'll simply need to:

• find out where these apps are used in your server instance and for what purpose;
• define if this functionality is business critical for your team;
• as the app assessment tells you: reach out to the vendor of the server app to find out if there is any way to migrate the features to cloud manually;
• seek alternatives if this is not the case
• come up with a plan to migrate / replace / drop some of these features 

[Arvind Swarnkar]

Hi @Walter Buggenhout 

Thanks for your detailed response.

Yes we are in testing phase.

here AdminOnlyFields and AssigneeNotEmpty are custom modules developed and customized through code in Jira server. 

If you could help me how to write custom code/Custom plugins on Jira cloud,

Any provision for Database access in Jira Cloud.

Thanks.

--arvind

[Walter Buggenhout]

Cloud has automation rules as a built in feature and that - as well as standard workflow conditions / validators - may allow you to cover a lot of the automated stuff people used to do on server.

I can tell you that cloud has 2 development frameworks, connect and forge that let you do custom development. But be aware that the platform is technologically completely different than server, has a lot of capabilities that did not exist on prem or are done differently and that you should NOT try to just replicate what you did over there.

Also, forget about access to the database. You don't have it in cloud. If you want to manipulate data, that goes via the REST API.

I would strongly recommend you to go to the drawing board first to list the features you have currently built, determine if you really need those, check if you can implement them in cloud using native functionality and only after that start looking into custom solutions.

You may want to seek help by engaging a solutions partner in your area. They offer (commercial) services that may help you save lots of time and headaches in helping you migrate.