Florian Bonniec Community Champion

Hi @Bridget Caci If you set the field required on the customer portal, it should be required. Not sure but does this field has a default value in the field context ? Regards

HI @Srain Zhou I do not have much solution for Cloud except using swimlane by Epic and searching in the page for the Epic Key. Regards

Hi @vincenzo.spatafora 401 means permission issue, you are not authenticate. Are you sure to provide the right Authentication param ? Regards

Hi @Kesava Ginjupalli You could set up the DVSC connector with gitlab named Development panel. https://docs.gitlab.com/ee/integration/jira/#jira-development-panel The integration you set up in Gitlab side seems to only check commits and merge requests. Regards

Hi @carlos andrade It could be fields that have user specific project permission on it such as Due Date or is it customfield ? Regards

You should not add the script in link field, you should add it on the Initialiser section, Create Script and paste it there. By doing so the script will be call when the screen open. If you let it in linked issue field, it only trigger when you update the field. Regards

Type error so it should not be the cause as despite the fact that we did not specify it, we are using the right one. I also have this error on my side. Could you share the entire configuration of the behaviour and hide if require sensitive information ?

It should only be a warning no ? It's because we did not use type for the list. It should not impact runtime.

Did you set the script as Initialiser and set the proper Mapping to enable the Behaviour on it ? This one works for me import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLinkTypeManager import com.onresolve.jira.groovy.user.FieldBehaviours import…

Hi @Marie-Josee Parent Could this help you ? https://confluence.atlassian.com/servicedeskcloud/blog/2017/05/translate-your-customer-portal Regards

Before continuing investigating, are you speaking about More > Link or the Linked Issue field ?

Could you try the Permission helper on that project to make sure it do not have pther access than the Portal Access permission ? Regards

No the permission is named "Service project customer - portal access" on DC. It's an option with Role, Group etc when configuring the permission scheme. If user is not listed in any role, and "Service project customer - portal access" is set the user should not have access to the portal because "Service project customer -…

Hi @Nadine Schuett With "Customers who are added to this service project", user from any role will be able to see the portal, if portal access is set. Could it be because they may be added as Customer in Organization feature ?

Hi @Karl Samson What is the error returned ? Regards

Hi @Tejas Naik You always need to test the upgrade on a test environment first. But, it should be ok. We migrated from 8.20.X to 9.12.X . Make sure to review each app if they have a breaking change but from 9.4.6 I do not except major change. Regards

Hi In order to achieve this you will need an app. It could be Scriptrunner with Behaviours,ProForma or Dynamic Forms. Regards

Did you properly configure the Issue Type Mapping section ?

Hi @Owen Have you added the project to the Requirement project in the Xray configuration ? https://docs.getxray.app/display/XRAY31/Requirement+Projects And added the type to the requirement configuration ? https://docs.getxray.app/display/XRAY31/Issue+Type+Mapping Regards

HI @Magnus Norberg You can define the SLA behaviour in your project admin page, SLAs. Regards

You could try something like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.fields.CustomField def earliestDate = new Date().plus(5) def dateField = getFieldById(fieldChanged) def dateValue = dateField.value as Date if (dateValue < earliestDate ){ dateField.setError("Date cannot…

Hi @Susann Ivarsson You could use something like this import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.fields.CustomFielddef earliestDate = new Date().plus(5)def dateField = getFieldById(fieldChanged)def dateValue = dateField.value as Dateif (dateValue < earliestDate…

Hi @Lipika Singh If you do not need to select them in Affected Version field either you could archive such version. By doing so no one will be able to select the version anymore. Tickets with this version will keep their value. Regards

HI @khushboo_puri You cannot do that the solution would be to create multiple transition, 1 with the condition of the field empty with the transition screen + validator and the second one with condition on the field and no transition screen. Regards

Hi @Lucas Z It's not really recommended but you could try to disable the export module (Plan Export Servlet (rm-plan-export)) in the app. If you choose to do it, make sure to test in a test env before. Regards

Hi @Josef Sigl You could try currentUser.isInGroup("AT_CPBS-Kunden(Alle)") Regards

Hi @65416 I would create an automation for JIRA for this. Regards

Hi @Taylor Huston On my side I'm using https://marketplace.atlassian.com/apps/1211756/timepiece-formerly-time-in-status?hosting=datacenter&tab=overview Regards

Hi @Patrick Schneider I do not think there is any native feature for this. If there is only some event you are interested in I would suggest to create an automation for JIRA for each of them. If you have a lot of events, updates, transitions, worklog etc. I would create a Script listener on All Issue Event and I would…

You can define the type of board at the board creation, it's the first step asked to the user who create the board. You can copy the board, from the board you want to copy, on the top right, Board > Copy. Creating a board | Jira Software Data Center 9.15 | Atlassian Documentation Regards