Ste Wright Community Champion

Hi @javierdvegu Just to provide a second point of reference - I tried this with a Company-managed Project and it performed as required. Team-managed only worked when I used the Status ID, rather than the word itself. You do mention above though that you've tried this. Given this bug seems to be intermittent, I'd suggest. *…

Hi @Jeff Shepherd That's not native behaviour. It sounds like you might have an App, such as Handy Macros for Confluence (which I think has this function). You could disable the App - which would stop this function from appearing. Or if it needs to remain "on" for other reasons, or it looks like you can disable it from…

Hi @Garden16_ I just tried using the Field Configuration Scheme for this - and it removed it from the View Issue Screen. Are you sure you've set the Field Config against the right Issue Type? Alternatively, the Script Fragment in Scriptrunner should work for the View Screen - set the details as follows: * Fragment: Hide…

Hi @Joseph Green You can add a Condition after the "Lookup" Action This worked for me: * Trigger: Scheduled * Action: Lookup Issues * JQL = <Query here> * Condition: Advanced Compare Condition* First Value = {{lookupIssues}} * Condition = does not equal * Second Value = Empty * Action: Send email ^ The audit log will still…

Hi Heather The process in this comment above still works - did you manage to find this option in the end? Ste

Hi @Tenzing Doleck My suggestion is a native workaround - utilising a custom "Description" field, which then copies the data back into the standard system field post-creation. There might be a small delay where the Description is empty - but it should be a very short period (i.e seconds). I use an Automation rule rather…

Hi @Jim Sheedy It's possible - an alternative to the above smart value for last comment is... {{issue.comments.getFromEnd(0).body}} ...but, you can change the "(0)" to get other comments also. So for example... * (1) - second to last comment * (2) - third from last comment * ...etc It's dynamic so will update as you add…

Hi @Michael Kornatzki Are you still facing this issue? And none of the above suggestions could help (especially checking page restrictions)? Ste

Hi @Zachary Paulsgrove There's a suggestion for this you can vote/comment on - see CONFCLOUD-38722 Quite an old request though, looks like it originally started as CONFCLOUD-4087 back in 2005! Ste

Hi @Samuel Stephens It should still work, I haven't needed to use it in quite a while though. DC has more options though, depending on what Apps you have - for example... * Scriptrunner (or a similar scripting App) would allow you to restrict available Issue Types per Group/Role - see this Scriptrunner help page as an…

Hi @Maria Andrea Famini This seemed to work for me: * Trigger: <<Trigger Here>> * Action: Lookup Issues* issuetype = <<Sub-task Issue Type>> * Action: Edit Issue* <<Field>> = {{lookupIssues.size|0}} ^ The Field above is a numeric field. Lookup is a more dynamic option when you have custom information to include. Ste

Hi @André Matzke I'm not sure what view you're referring to here. Could you provide a screenshot to demonstrate the issue? Ste

Hi @Kim Cary It's not a drop-down menu, it's a searchable box which provides results as a list. If you're receiving no results I'd recommend typing it in slower, or just one of the names - see what it can find. You can also test it with others users, or on other Projects, to see if this is an issue across your wider…

Hi @Amy McCann I just tried... {{issue.fields.project.projectCategory.name}} ...and it works for me. Assuming you've checked the Project has a Project Category, could you give us the full rule details so we can try to replicate your issue? Ste 

Hi @Ben Vandenbosch I had a look at your other post, and placed a more detailed answer there :) Ste

Hi @Inna S I'm not sure how you're calculating 25% refund unfortunately. Atlassian operates a SaaS platform - and like most large companies in this space, does suffer some incidents - and are very transparent about them (as seen from your link to their status page and incident history). But from my experience, significant…

Hi @Matt Houck Yes - the hierarchy should not break if you are adding... * A hierarchical layer above the existing hierarchy (i.e CIT) * Additional Issue Types into existing layers, but not removing any (i.e Milestone) ^ Of course, there are circumstances where you could break it - for example, adding a layer inbetween two…

Hi @Mitesh Shah I'm not sure I understand, can I clarify? The Status "Assigned to Technician" is when the time is counting down - and during this time it counts to 0, and breaches SLA. Isn't the reality that it's a work in progress - but hasn't been closed within the SLA, so is in breach? What alternative action are you…

Hi @Sreenadh With all the different schemes/configuration taken into account, there's no release mechanism to move this to another instance natively. I'd recommend re-building it manually. Ste

Hi @Moubin Patel Could I clarify the need here? Where are you trying to add the Product Category and Approver drop-down? Is this in a Request Type (i.e customer facing)? Or is it for Agent usage? Ste

Hi @Jon Bowes Wouldn't it be easier to direct the users to a specific Jira Service Management link? For example, the direct link to raise the required ticket type, embedded as a hyperlink or similar? Ste

Hi @Stefannie Tan Do you mean in a Board? I envisage removing them could impact reports/data views - but it will come to if reports from previous years are still relevant, or if their removal could impact current/future reporting. * If yes, you can keep the dates on there * If no, it'll be fine to remove them Ste

Hi @Earnest Angel Have you tried doing this on another browser, or on incognito mode? It could be a cache issue or similar. Ste

Hi @Oscar Nancy It's likely if it was widespread, we'd be seeing a lot more posts! Is this now resolved for you? If not, could you provide screenshots to better visualise the issue? Ste

Hi @Samuel Charpentier Have you tried the instructions on this page? https://support.atlassian.com/jira-cloud-administration/docs/use-applinks-to-link-to-atlassian-products/ Ste

Hi @František Vůjtek Can I confirm that you have: * Issues links directly to the ESC issue * Further issues linked to the "linked" issues above, which should also close (i.e a secondary sibling) So when ESC closes, all the issues - either direct or indirect - should close? Some basic questions first: * Are the secondary…

Hi @Adrian Bogacz You could probably use Jira Cloud Automation for this. Advanced Roadmaps utilises data from Jira - so for example if... * Issue A blocks Issue B and... * Issue A is not complete by its due date Then you could change Issue B's due date to be 7 business days later. For example, the rule might be... *…

Hi @Vincenzo Ciaravella I know this isn't the direct question - but would it not be easier to move the other rule to Project Automation, even if it has complex formatting? Automation will work fine when the two rules are no longer in Legacy - and the effort to make the Legacy rule work could be spent moving the rule…

Hi @Daniel Cave Not that I know of natively. The Jira Filter macro is effectively referencing Jira Search / JQL - so cannot take into account the Confluence page name, or any wildcard capabilities to that effect. Ste

Hi @Ben Vandenbosch I'm afraid not - it allows issue linking between instances, but isn't visualising the data for use in Plans, reports, etc. You'll need all the data on one instance to use it with Advanced Roadmaps. Your options here are to either... * Migrate the users/data - depending on how painful it is to report…