Kris Dewachter Community Champion

Hi @Roberts Čāčus - eazyBI , I did not notice the space error. *embarrassed*. The result now looks much better. I get the correct calculations. However, I wonder if it's possible to have the "Cumulative Available Days" start counting from today's date, and not take the historic days into account. When I set a filter on…

Hi @Roberts Čāčus - eazyBI , I tried the standard calculation, but something is not going correct. This is what I have so far: * Vandaag = Current Date * Remaining Estimated Days History (Remaining effort in Days) * AvailableDays = Number of workingdays per week. This is imported from a Google Sheet * Cumulative…

Hi @Roberts Čāčus - eazyBI , Thank you for your feedback. I've been working with your suggestion for a few days, until i realized the report is not returning the results i need, and maybe i am making things too complicated. Let me try to explain again. I want to predict on what date a project might get finished. I have 2…

Hi @Ed Clarke , Just to recap for my understanding ..... You have 2 service management projects in the portal ? In the permission schemes for both projects, the "Browse Projects" and "Create Issues" permissions are both assigned to "Service Project Customer - Portal Access" ? The customer is able to see both projects in…

Hi @Anna Debono , Unfortunately, you can not set permissions on the request types in the portal. If a customer has access to a project in the portal, they will able to see all request types. I think in your case, your best options are to: * Create separate JSM projects in your portal, with different permissions * Add some…

Hi @Ed Clarke , Are you creating these new tickets also in a Service Management project, or a Software project? If you are creating them in a SM project, you will need to make sure the 'Customer' has the 'Create Issue' permission in the permission scheme. If you are creating the new ticket in a Jira Software project, you…

Hi @[deleted] , When you use the 'Edit Issue' action in your automation rule, you can select to edit multiple fields in 1 step. Best regards, Kris

Hi @Troy Edmonds , You can create a custom event. Please have a look at this documentation: https://community.atlassian.com/t5/Jira-Service-Management-articles/Disable-email-notifications-for-a-specific-transition/ba-p/919541 Best regards, Kris

Hi @Lucas de Souza , Can you try 1. project in (xxx) AND status in ("pending", "waiting for customer") AND status changed before -2d 2. project = XXX AND status = "Waiting for approval" AND NOT status changed AFTER -2d 3. project = XXX AND status in ("Pending", "waiting for customer") AND status changed before -5d) Best…

Hi @MURUGESH S , Unfortunately no, not by default. You might need to look at an Addon to make modifications to the layout of the portal. Best regards, Kris

Hi @Ashutosh Meelu , You can not setup an separate portal, but you can setup a separate project within the existing portal that is only accessible for external people. Best regards, Kris

Hi @Archana Mattoo , I would create an automation rule to fill the fields after ticket creation. You can extract the values for "Host" and "Node" by performing actions on smart values. Please have a look at these options: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Best regards, Kris

Hi @cheikh charles ndiaye , You mean hiding them in the Jira Backoffice ? Only way I see of hiding those issues is to setup Issue Security. https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html Best regards, Kris

Hi @alison.perez , No, you can not redirect to another page after submission. Best regards, Kris

Hi @Aaron Aldridge , I don't think you need an automation rule for that. On each request form, you can add fields and make them hidden. You can also assign a default value to them. Like this, the fields are filled, but not visible on the form in the portal. Best regards, Kris

Since permissions are defined on Object Type, you will have to create separate Object Types. But maybe you can use inheritance to create main- and sub-object types and set the permissions on the sub-type ?

Hi @Sarah Edell , As far as I know, you can not set permissions on individual assets. I guess the only option is to configure 2 separate object types. Best regards, kris

Hi @alison.perez , You can't disable the links. Not without an additional AddOn anyway. Maybe it's better to create a 'Form' for this request, and in the settings configure it so the form can be used to create a new issue. You can then access the form with a direct link outside of the portal. Best regards, Kris

Hi @Mihir Ruparelia , These smartvalues should work: * Fixversion : {{issue.fixversions.name}} * Startdate : {{issue.fixversions.startDate}} * Release Date : {{issue.fixversions.releaseDate}} Beware that an issue can belong to multiple versions. If that is the case you might need to loop over them. Hope this works. Best…

Hi @Galiya Muratova , I'm afraid you won't be able to visualise this with the default tools. You will need to use some third party reporting tool. Best regards, Kris

Hi @aya el youssoufi , First, you should create a custom field of the type "Group Picker (single group)", and make sure this can be used when creating or editing a ticket in your project. This can be used to assign a usergroup to a ticket. Secondly, you can create an automation rule that sends out the email. Make sure it's…

Hi @Cecilia Quintero , What do you mean with "user view" ? Do you mean the portal ? The extra functionality will only be available in the Jira backoffice for agents to use. Best regards, Kris

Hi @Mihir Ruparelia , Yes, I think this is possible with an automation rule. If you have a JQL that retrieves the unreleased tickets, you can use this to retrieve the tickets in the automation rule. And then in the automation rule use the action "Create issue with a request type" to create the ticket in the service…

Hi @Bernd Anderer , I think the easiest solution is to create an 'if/then' condition in your automation rule on the "issue.customfield_10273" If "issue.customfield_10273" = Yes Then Use the "Create Variable" action to create a new Smart value and fill it with "True" Else Use the "Create Variable" action to create a new…

@Jimmy SeddonFeb. 2nd please.

Hi @Bernd Anderer , What is the process exactly ? The "Ja", "Nein" select field is part of an issue ? The issue triggers an automation rule that performs some action on an asset object ? Best regards, Kris

Hi @Ravisekhar.g , I don't see a way to duplicate the form itself. However, as a workaround, you can select to have the form of request A saved as an attachment to the ticket. Then, to create request B, you could 'Clone' the issue in an automation rule, and copy the attachments in the clone action. Best regards, Kris

Hi @Harry Schilbach , Just create an automation rule that is triggered upon issue creation. You can add the "Delete attachments" action. There is the possibility to specify in detail which attachments you want removed. Best regards, Kris

Hi @Alicia Ochovo , At the moment, I see 2 possible causes. 1. It's possible that Atlassian prevents Asset fields to be visible for non-logged in users. This page about users. https://support.atlassian.com/jira-service-management-cloud/docs/set-up-the-assets-object-field/ So maybe it only works for logged in-users. You…

@Evert Morren Atlas Admin, I don't think this is possible. Best regards, Kris