Ste Wright Community Champion

Hi @ingvarr You could create a suggestion for this? You can do so here: https://jira.atlassian.com/secure/Dashboard.jspa Ste

Hi @Tatiana Marti It's not possible to order by status category unfortunately. You can order by Status order though - the order is based on the order of Statuses within your system (i.e Jira Administration > Issues > Statuses) ASC is classed as top > bottom of list. Ste

Hi @Jira Admin There's no additional cost you can spend to increase the number of SLA goals per project - the limit is actually documented as 90 so you're already above the norm. I'd recommend... * Looking if you can consolidate any of the goals - giving you the option to have more goals to utilise * Contacting Atlassian…

Hi @Sandesh TM Dates fields don't work with "=" that often, as they're captured in the system as date/time. You need to use multiple validators to get a specific day - eg. * Date is >= Start of Day AND * Date < End of Day What's the logic you're trying to validate specifically? Ste

Hi @Siobhan Wallace No - you need Atlassian Access to enable SSO. Unless you happen to use Google / GSuite, then see these instructions: https://support.atlassian.com/provisioning-users/docs/connect-to-g-suite/ Ste

Hi @Lucas de Souza You can do this using Automation. You need to create the Template page first, which will be used to create the page: * Go to Space Settings * Under Look and Feel, select Templates * Select the Create New Template button in the top-right corner, and create the Template Next, you can create the Automation…

Awesome! Let us know how it goes :) Ste

Hi @清水　佑菜 Can I ask why? The need might drive the answer to a degree. Ste

Hi @angela Not at this stage unfortunately - the People screen in a Project only accepts single users or Groups. Groups is a good alternative though as you can create a Team as a Group, and then assign that rather than individually adding each person. Ste

Hi @Kunal Thakale How is the Action setup? A screenshot of that would be useful here. Ste

Hi @Ayush Lawania It might look something like this: * Trigger: Issue Created * Condition: Issue Fields Condition* Field = <Unique Field> * Condition = equals * Value = Yes * Action: Clone Issue ^ In effect, the rule would check that an issue was created with the unique field flagged as "Yes" this was created from a form,…

Hi @kedar It's going to be complicated if the field could be "anything" in terms of duration. I think you'd be better to... * Have a duration field for a set type of duration - days, weeks, etc - which can be consistent * Use that to set the dates using Automation ^ That would be an alternative method to what you've…

Hi @Daniel Weinberg If the products are available for you, you will find them here: * Go to https://admin.atlassian.com/ * Select your Org (if you have more than one) * Select Settings from the top navigation bar * Choose Atlassian Intelligence from the left-hand column * Press the blue Select Products button * Activate AI…

Hi @Kathryn Gerrell It might be useful to use 2 Projects for this - for example... * JSM: Front-door for the requests - users can make requests, and get updates from the Finance team * JSW: Private Project where Finance team action tickets ^ You could then do the following... * Automation: Clone JSM Tickets into JSW…

Hi @Remco Streng Not that I know of - but you could provide this as feedback? * Select the breadcrumbs (3-dots icon) in the top-right * Press Give feedback Ste

Hi @bhushan I think it'd be easier to just add the default user access Group to the Project Role in that Project - then all users would get access that way? Or if it's multiple Projects, add them to a Group during issue creation, and have one Group per Project Role instead. Would that work? If not, could you provide more…

Hi @Zach Bowen Couldn't you add this to the Issue Security Scheme? For example... * Add a custom User Picker field * Set the Assignee to that field, rather than Request Participants * Add the User Picker field to one of the Security Levels You could make the User Picker more secure by keeping it off the screen, and…

Hi @Amatul Maryam Can I clarify, you need a Dashboard which highlights if the Assignee was changed between "Ready to Build" and "Done"? If yes - you need a field to visualise on the Dashboard or filter the Dashboard on. You'd have to create this metadata as part of the Issue's journey to Done. I would... * Create a Custom…

Hi @Ray Letoa I don't think so - the notification is just an alert that an event happened on the issue. You can respond to an email which is sent as a customer notification when a comment is added to the issue - and it can add an comment back. Could you do something with this? Ste

Hi @pavel.ryzhykau Not that I know of - this is relatively new functionality at this stage. You could make this a suggestion though? You could do that from here: https://jira.atlassian.com/secure/Dashboard.jspa Ste

Hi @tapeesh Yes you can: * Select issues using the checkboxes on the left-hand side* You can select "all" using the top checkbox * You can also select a group using Shift + Click (top/bottom checkbox) * When selecting multiple issues, a Bulk actions box will appear in the title row - select Release from this dropdown * Set…

Hi @Thomas Wilson This seems to work for me: project = ABC AND issuetype = Epic AND component = "EPIC Schedule" AND labels = Afloat AND issueFunction in hasLinkType("Epic-Story Link") AND issueFunction not in epicsOf("summary ~ 'Submit COP'") Ste

Hi @Chris Campbell I'd give opsbar-sequence a go: * Edit your Workflow * From the Diagram view, select the transition you want at the top - and from the pop-up, select Properties * In Property Key, enter opsbar-sequence * In Property Value, enter 10 * Repeat this process for the bottom transition, but enter the Property…

Hi @kedar Just to confirm... * You have a custom number field - Duration * When entering duration (in weeks) into the field, you want it to set the Start/End date based on now (start date) and N weeks time (end date) ...is this correct? Whilst not directly possible in Advanced Roadmaps - you could use Automation for this.…

Hi @Andre Heyen Is this working for you now? If yes, it could have been the outage that took place on Sept 28th - see this page: https://jira-service-management.status.atlassian.com/ It might be worth contacting Atlassian Support to get a firmer answer - you can do this from here: https://support.atlassian.com/ Ste

Hi @Christy Johnston You need an email address for the account to be a Managed Account - so it can verify against the domain. Ste

Hi @Ayush Lawania You'd need to have a field on the Form which is unique to it - to trigger the Automation rule. But as JWM Forms are quite simple, it's not as easy to do this as there's no way to make a field mandatory only on a Form, or hidden with a preselected value. It might be better to use Jira Service…

Hi @Adrian Joshua P. Dela Cruz What's the exact need here? Is it... * On Issue 1, you enter 2 Components * If Component 1 is added, create Issue 2 * If Component 2 is added, create Issue 3 ...? If not, could you explain it in more detail? Ste

Hi @christian held Not that I know of - it's showing you the title of the ticket in the customer view, rather than the unique identifier (which I assume Atlassian sees as more important to a customer). You could use Automation to put the Key in the Summary field if you like - something like this... * Trigger: Issue Created…

Hi @Alena Podmanicka There's a few things I would check out here: * This help page, on how to integrate Jira Cloud and Slack - https://support.atlassian.com/jira-service-management-cloud/docs/use-jira-cloud-for-slack/ * Setting up notifications for your customers and your internal team…