Jovin Community Champion

Cheers @Tomislav Tobijas glad you could attend (so close on the gift card!)

Thanks @Susan Waldrip ! Hopefully we can continue to contribute meaningfully to this community!

@Marc -Devoteam- Cheers for that, went into sandbox and did some testing using the “log in as user” through the directory. Looks like visibility remains for existing issues, unless the login in as user retains some kind of elevated access (I don’t think so)

Did some testing on Sandbox and as far as I can tell it looks like existing requests that then become restricted remain viewable by the reporter, approvers & participants. Test steps: * Logged in as customer (non-Admin) * Raised request type * Switched to admin and restricted the request to _no-one-at-all * Logged into…

Thanks @Marc -Devoteam- I made sure it was an edit field and combined with Aaron's comment allowed it work work :) 

Thanks @Aaron Pavez _ServiceRocket_ ! That worked a treat!

Hey @Ásta Hrönn _RdN_ ! With JSM this is not too difficult at all! You can go to the Project Settings and then into Language Support from here you can add the language pack you need. Then I'd recommend you use Forms for all of your request types though as it allows for super easy translation. When you've designed it you…

Another 700 club member here 👋🏻 On 723 days. I've been on a life long language learning kick, but can only speak basic level in 1 language other than English... a history of my timeline: * Pre-Primary School: My father attempted to teach me 🇮🇸 Icelandic (his 1st language), but unfortunately learning it in Australia meant…

Hey @Andrea Italiano There's no way to disable accessing the Portal without removing them as a customer of the Portal. If you have multiple service projects you can restrict it so it's only customers invited to that project, but that once again gives them access to the Portal. By default the notification scheme sends…

Hey @Ann Rumenapp You could use an automation rule to achieve this. Meanwhile it doesn't make it read-only or required etc. it can help enforce things. Automation Rule - Prevent Changes by Anyone Other than the Approver This rule will prevent anyone other than the person in the Approver field from changing the fields you…

@Santhosh Raj - Custom fields only allow 2 levels (A->B), and the new feature on the roadmap is bringing that configuration to Forms. There is no way to have a 3-level cascading field. When the 2-level ones come into Forms you can condense the above slightly: Cascading Select List 1 --- Section: Conditional: Select List 1…

Hey @Santhosh Raj Currently the forms that can be displayed on the Portal do not allow cascading fields. That is, however, a feature on the Roadmap: https://www.atlassian.com/wac/roadmap/cloud/cascading-fields-in-forms?selectedProduct=&search=casc&p=96ced183-30 For the time being a workaround solution would be to have a…

Hi @Maurizio Monti You should contact Atlassian Support about this query. https://support.atlassian.com/contact/

Hey @Michaela Kelle-Emden Should be achievable, just depends on the individual configuration you have. Can you help me with understanding the below: * How do you identify a "Rejected" issue? * Are you looking to sum the story points onto the Epic?

Hey @Nandhini M You could always get around this by making a blocker on the workflow and an automation to manage that blocker. Stay with me! Step 1: Prohibit marking a ticket as Done if no time has been logged * Create a custom field for your issues called "Has time logged", it should allow "Yes" and "No" options, with the…

Hey @Digvijay Singh Gehlot Interesting use case and meanwhile I haven't investigated the use of conditions & post functions for this, you should be able to achieve this with the use of Automations and hidden custom fields. My solution below: * Create a new custom field called "Can Prioritize" as a Select List (Single) with…

Hi @Doug Monk The indication to contact Atlassian is correct. By doing so you can speak to Sales/Billing who will be able to organise the annual plan and (if relevant) any discounts applicable (not guaranteeing that there would be). The community isn't actively monitored by the Atlassian sales/support teams, so this kind…

Hey @Jensi Toledo Atlassian Community is a group of users of the platform and not actively monitored by the Atlassian Support team. You'd be best off contacting them with your query at the link below. https://support.atlassian.com/contact/

Hey @Santhosh Raj You can certainly modify the fields displayed below that via the "Create Screen" for each of the issue types you have, this would allow enforced fields to be visible/hidden (https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html) But in terms of hiding that switch unfortunately…

Hey @Gaute Wardenær Great question and in terms of ways of working everyone has their own preferred method of doing so. My opinion is in alignment with your colleague - use the tickets to create, authorize, track and complete work, and confluence to track information on the clients' sites. Benefits of JSM would be: *…

Hey @Hannah Sorrell Great question here, and meanwhile I'm unsure whether the URL can be used to link it you can always give it a try by using the "Link issues" action alongside the smart value for the field. That dropdown can also have values typed in. To access the field you've created use {{issue.Field Name}}, in this…

Hey @Harshad Prajapati Dates can sometimes be quite frustrating to work with in Automation Rules, however, if you're looking to set it to the time of the rule triggering you should be able to just use {{now}}, like in the screenshot below. I've used "Due date" because I don't have a reopen date field.

Hey @金奕开 Just thought I'd check in on the steps taken so far - I see you mentioned "Portal" but not sure if you're referring to the Jira Service Management Portal or not, so let's check out what's happening. For Jira Software that document you supplied should work without issue, as it will for Jira Service Management too.…

Happy to @carolyn french ! It's been a great journey and the Ops Excellence coaching was by far one of the biggest periods of growth knowledge and stepping outside of core IT work that I've done, it was phenomenal! I see you already connected on LinkedIn - let's not be strangers!

Hey @Jason Weddell I've encountered that as well! Not being able to remove statuses as it's not draft! You are correct in that we need 2 separate workflows for the issue types. Option 1 - Aligning with my Suggestion So be sure to have that new issue type added to your project as…

Hey @Jason Weddell You can achieve this most simply by creating a new issue type and apply it to that, I'll call it "Scheduled Request". You should then add a new SLA criteria ahead of the "All other issues" in your SLAs and have the JQL below: issuetype = "Scheduled Request" You'll also want to have a slightly different…

Hey @Jens Prokoph Sounds like you need to modify the existing automation to look only at a specific project so it stops looking at the new project. You'll find this setting in the "Rule Details" section of the rule, but you'll need to be in Global Administration for this to work (there is a link on the Rule Details tab…

Hey @Mathilde I see you like the solution I proposed, if this helped it would be wonderful if you could select it as the answer! 🙏 Have a lovely day! 

Hi @Devoloper It's possible that the x509 certificate was copied from an incorrect source, or it has actually expired. In the Entra ID configuration you'll need to generate a new certificate and update your IdP settings in Atlassian Guard.

Hi @Mika Barnett-Ohori In terms of storing this value on the ticket you could use an automation rule such as below: * Trigger: Field value changed* Field: Rule ID * Operations: All * Condition: Issue field value* Field: Rule ID * Condition: IS NOT EMPTY * Action: Comment issue* Content of comment:…