Issue view screen is too different in Jira Service Management than Service Desk(Old Jira)

[Amit Kumar Singh]

Now we are migration to Jira Service Management (Cloud) from Service Desk(Old Jira), created new project and all the issue types, fields and screens, facing issue with below few points:

• Issue view screen is too different in Jira Service Management than Service Desk(Old Jira).
• Unable to create Message Custom field for edit screen to show the headings for few fields on each tab for customer understanding.
• Scripted fields
• Unable to use html in message custom field for default value to show as heading
• Unable to show multilevel cascading field on Request Types for customer portal

[Nic Brough -Adaptavist-]

Hi Amit,

• Jira Server and Jira Cloud are different pieces of software, they diverged years ago, taking two different routes along how to visualise issues.  You can't expect them to look the same.
• Your second screenshot is of the configuration of a Team Managed Project.  These do not support message fields.   (Also, company-managed projects look a bit more like server than team-managed ones)
• Cloud does not have scripted fields natively.  Scriptrunner can add them (in Company Managed projects), but they work very differently to the server ones.
• Cloud does not allow for HTML injection, it's not secure and Atlassian do not want to have to support systems where you do it.
• What app are you using to create multi-level cascading selects?