Dave Mathijs Community Champion

Maybe the board is too complex. Don't hesitate to submit a support request with Atlassian directly.

That would be a camel (dromedary) ride when on vacation in Tunisia in 2010.

Hi @Paweł Partyka Are you in a company-managed or team-managed project? Does your status Review set a resolution, either via a post function in the workflow or via a validator with Resolution as required field? No matter the status category of a status, in this case Done, a resolution is required for Done statuses as…

In case of a team-managed project, you can only group by: * Assignee * Epic * Subtask Epic is only visible when it's defined as an issue type within the project. So no real swimlanes here.

@Emanuel Nieto Thanks to click the green Accept answer button if the answer above was helpful.

To my knowledge, this is not possible. Do you have other base issue types in your issue type scheme? There are no validators either that can be used to restrict this. You watch can vote for suggestion JRACLOUD-44557 though. It is possible if you have the ScriptRunner app installed: user.groups.includes("Group 1")…

Hi @Zara Hughes The issue hierarchy in Jira (and therefore Advanced Roadmaps) is very strict. You cannot "add/insert" an issue type above Epic without changing the hierarchy. If you were to add issue type Key Result directly above Epic (level 2), then it would change the hierarchy for the current level 2 issue type,…

Hi @Verena Ruff if you are part of the group confluence-administrators, then you should be able to change the page restrictions for those pages.

Hi @Bezi welcome to the Atlassian Community! Are you able to open that specific board in the browser version of your laptop/desktop? Are you a board administrator, project administrator or jira administrator?

Hi @Sunilkumar k The Add a child issue button is available within an Epic: It allows you to create a child issue (Story, Task, Bug, custom base issue type ...) within the Epic.

Thank you for sharing @Summer Hogan !

My earliest memories go back to kindergarten. Seeing how another kid got his fingernail stuck between the gate with its nail hanging loose from the finger - it was bloody too - was quite traumatic at the time. I imagined how painful that must have been. And on another occasion, I remember wondering for hours how on earth…

@Carlos or @Vasily Kasatkin You are in a company-managed software project, right? Could you please share a screenshot of the board settings of your kanban board? It should look like this:

Thank you for confirmation @Bhaargavi Natarajan 

@Dori Burnett I just received an e-mail to notify me that my registration has been cancelled now stating that the event is not available for non-sponsoring partners. Very disappointed that this has not been made clear upfront. Atlassian knows who its sponsors are, then why open up a public registration website? What about…

@Avinash Gulumbe That is normal behaviour as the fields in Jira Service Management back-end have their original names. If you want these names to be changed for agents as well, then you need to edit the name of the custom field.

Hi @Amali welcome to the Atlassian Community! Why don't you deny comments on a closed issue via a workflow property instead?

Hi @Ronak Patel For the transition: You can add this field to the transition/workflow screen and add the Field Required Validator as validator.

Interesting story and context about floriography @Hana Kučerová , I never paid attention to it before.

Hi @ElHabib_DAMANI welcome to the Atlassian Community! In that case, contact Tempo support quickly as they are able to re-initiate the migration of the worklogs manually. Unfortunately, I've experienced the same issue and I wonder about the first-time succession rate of Tempo worklog migrations via JCMA.

Hi @Berat Altunhan , the only way to achieve this is to remove all these fields from the Edit issue screen and move them to the respective transition/workflow screens between the statuses (so on the transitions) where they may be editable. You cannot show/hide fields on the issue view depending on the issue status.

Hi @gcapdevila portal-only customer accounts are not able to comment internally as a Jira Service Management license is required. If you customers have an Atlassian account and product access to Jira Software, then they are able to make internal comments on a Jira Service Management issue. The only way to avoid this is not…

Does this mean we can have different workflows for different request types with the same issue type? If you have 2 request types using the same issue type and you change the workflow of the first request type, will the workflow of the second request type also change?

Can you share a screenshot of a request type configuration with the correct display name and the same request type in the portal showing the incorrect name?

Hi @Avinash Gulumbe welcome to the Atlassian Community! Did you update the display name of the fields? Please note that these are only visible in the customer portal (for customers), not within Jira Service Management (as an agent).

Hello @Christine Bösel have you been able to test the query?

 I'm not a traveler myself, but inspire me with all your destinations ...

Very exciting, got my head in the Cloud.

Wish it were available for (at least) Premium plans as well ...

Hi @G Naresh I'm not aware of such a solution. To whom might it be of interest?