nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Known Issue

Can Akkaya

Issue description: Portal customers are unable to see the description field in the customer portal when tickets are moved across service desk projects by agents.

Atlassian confirmed that when the issues are moved from one project to another it usually causes the Request Type Mapping to break.

Accepted answers

Dave Mathijs

Hi @Can Akkaya welcome to the Atlassian Community!

When moving an issue between service projects, the actor can map the issue to a request type of the target project.

Do you have a specific question?

All comments

Dave Mathijs

Hi @Can Akkaya welcome to the Atlassian Community!

When moving an issue between service projects, the actor can map the issue to a request type of the target project.

Do you have a specific question?

Can Akkaya

Dear Dave, thank you for your value feedback. We got it done as you mentioned and seemed to come in handy. But after creating a few Jira tickets n the same account then the issue had been repeated its self. So we have the same point.

Dave Mathijs

Is the Description field a required field in one project or the other? (in the field configuration)

Can Akkaya

HI Dave

there is no reqired description field in one project or the other?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management