Ste Wright Community Champion

Hi @Leslie Hicks I don't believe so when using the keyboard shortcuts - but the comment section does let you choose what type of comment you want to make (before you start commenting). There is a feature request for something similar - see: https://jira.atlassian.com/browse/JSDCLOUD-1928 Ste

Hi @Leslie Hicks If this is an agent making the comment on your internal platform, it gives you the option to choose internal or external comment. Are you say though that the customer is adding a comment in the customer portal, and this comment is defaulting to an internal comment? That's not native behaviour, all comments…

Hi @lindsay.makin Easiest way I find to do this is as follows: * On the top navigation bar, go to Filters > Advanced Issue Search * Search for your issues * In the upper-right corner, select the 3-dots icon * Select the option "Bulk change all N issues" - where N is the number of search results * Follow the instructions to…

Hi @Dd You're looking for a JQL query which will check if "now" is greater than 5 hours from the issue's created date? Something like this should work: created <= -5h Ste

Hi @Mattia Meneghetti Can I clarify what you mean by "automatically move on" the planned tasks? More information would be great! Ste

Hi @Vicki What type of Project is this - is it Company-managed or Team-managed? And is it a Work Management or Software Project? Ste

Hi @Disha Patil As far as I know, if you want to implement SAML SSO in Atlasian's Cloud products, you need to use Atlassian Access. See more about how to do this here: https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/ The only exemption is Gsuite, which…

Hi @Bayram Qasimov Field-level permissions aren't a native feature - there are a few options though... * If it's a field based on a permission (like Assignee or Reporter), you might be able to use a workflow property in a Company-managed Project * You could have the fields only editable on a transition screen, then limit…

Hi @אביטל ווליק For Team-managed, these instructions should work: https://community.atlassian.com/t5/Jira-articles/New-Feature-Different-Workflows-per-Issue-Type-for-Team-Managed/ba-p/1808647 I just tested this and it works for me! Ste

Hi @Vijay dumpala Not using the Assignee field, it is single select. What you could do though is... * Utilise the Team field for assigning a team * Use an Automation Rule to send those users a notification ^ You could also use a custom field to capture the team, based on Groups - and send the email more dynamically that…

Hi @אביטל ווליק Is this a Company-managed Project? If yes, you need to ensure there are at least two separate Workflows - one for the Epic, and one for the other Issue Types. You can then assign different Workflows per Issue Type using a Workflow Scheme, see how to do this on this help…

Hi @אביטל ווליק This rule should work: * Trigger: Issue Transitioned* To Status = Done * Action: Comment on Issue* See text below... --- Hello, this issue was closed! It was closed at {{resolved.shortDate}} It was closed by {{initiator.displayName}} --- A few notes... * This rule uses smart values * The closure of the…

Hi @Saro JAMKOSSIAN Could you explain your need in more detail? It sounds like you need two separate validators (one per transition), and two separate screens :) Ste

Hi @Dai G Are you having the same issue? That the tabs aren't showing on the view screen? Ste

Hi @Tim Rooney Paragraph is a Cloud term, it would be a multi-line text field in Data Center. But you should be able to just modify the system field itself in DC - and set the template that way. Ste

Hi @Rosanna Dill There's already a few requests for this! * Full Card Colours: https://jira.atlassian.com/browse/JSWCLOUD-21499 * Multiple Flag Types: https://jira.atlassian.com/browse/JSWCLOUD-2268 Ste

Hi @Sowmya V You'd need to create the field as a custom field, there's no standard "RAG Status" field. See how to create one here: https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/ Ste

Hi @Arielle Unterberger My original answer only works with issue links - not Epic Link (i.e Parent/Child relationship between Epics and Tasks). In this instance, I'd either... * Use one instance, and control access to them using permissions, or... * If this isn't an option, sync the two instances together and pass the data…

Hi @Amit Fainer Is this still not working for you? Ste

Hi @Aayushi Soni This is a 3 year old question; the option to disable the "new issue view" is no longer there - as the classic view was retired. However, the checkbox "Include subtasks" is now available on the current view, so the above instructions are redundant :) Ste

Hi @Piotr Maligłówka See the above instructions, which will help you locate it :) Ste

Hi @Brandon Mohl Do you mean the Action in the Automation Rule - i.e * Action: Edit Issue* Field = <Custom Number Field>* Value = {{issue.created.diff(resolved).minutes}} If yes, the value would go into the box next to "Time to Resolve" - this is a smart value, which will calculate the numeric value based on the rule being…

Best to watch this feature request for updates: https://jira.atlassian.com/browse/JSWCLOUD-17336 Ste

Hi @Alma Agic You can't - your Board can be either Kanban or Scrum, not both. I'd be careful having two Boards with the same data though - Boards are just visualising data from a Filter - so if two Boards have the same data, a change in one will be reflected in the other, and could cause confusion. Ste

Hi @David Goldberg As far as I know, it's still not available in Team-managed (formerly called Next Gen) Projects. It's still possible in Company-managed Kanban though (formerly called Classic) - see instructions in my comment above. Ste

Hi @Paul Nel As far as I know, Jira Product Discovery Projects do not have this option at present. Ste

Hi @Faisal Shamim You can - there's two native options. --- Workflow Validator Note: This only works for Company-managed Projects You can set which Statuses a Parent must be in as a validator for the "Create Issue" transition. This would let you "exclude" the Done Statuses. To do this... * Go to Jira Settings > Issues >…

Not that I've seen - but you can search and/or raise a new feature request for this here: https://jira.atlassian.com/secure/Dashboard.jspa Ste

Hi @Virgo Admin This rule should work. I've used "Blocks" as the link type: * Trigger: Issue Transitioned* To Status = In QA * Condition: Issue Fields Condition* Field = Issue Type * Condition = equals * Value = Bug * Branch: Related Issues* Type = Linked Issues * Link Type = blocks* Branch-Condition 1: Issue Fields…

Hi @Oriol Ortiz If you're following my recommendation above, and duplicating an existing Workflow - these are the steps: * Go to Settings (cog icon in top-right) > Issues * Select Workflows from the left-hand menu * Locate the relevant Workflow to duplicate - then on the right-hand side of the row, select the Actions…