Ste Wright Community Champion

Hi @Ajita Kopparapu Not natively, there's no field-level permissions in Jira. I've seen a few different alternatives used to do this, in particular... Workflow Screen * Add the field to a Screen only editable in a Workflow transition. This means it's only possible to modify the field during that Status change. * Split the…

Hi @Firdos Siddiqui Just to be clear, I don't work for Atlassian - I'm just a volunteer on the Community! Just to highlight this from above, I would recommend as a good next step to either contact... * Atlassian, specifically their migration team * An Atlassian Partner. Partners are able provide hands-on support for…

Hi @Gefrey Manohar Sure - I'd modify some of the design choices for this... * The rule needs to cater for a many-to-many relationship - i.e many Issues can block one Issue. * The first condition will check for related issues, rather than Issue Type, as any Issue Type can be linked to any other using a sibling relationship…

Hi @Shailesh Srivastava Strange! I tried this, and found if you add a second condition it becomes available. Could you try this to see if it works in your instance? Just to clarify on the condition setup from the screenshot above... * Field: This is the field the rule is aligned to * Condition: This is equals, not equals,…

Hi @Christophe Mes I'd advise contacting Atlassian Support via - https://support.atlassian.com/ Let them know you're experiencing the outage, so they can keep you updated with when your instance will be back online :) Ste

Hi @Tal.Elbaz This depends if you're on Server/DC, or Cloud! Server/DC, and Company-managed Cloud Projects In these instances, you can manage the setup of the Create Screen, separate to the View/Edit Screen. You'll need to be a Jira Admin, and then... * Go to Jira Settings > Issues * On the left-hand menu, select Screens *…

Hi @Eliakim F. Morais There is an active incident at present - please see the Status Page for more details: https://status.atlassian.com/ I'd also consider raising a ticket with Support - https://support.atlassian.com/ - so they can keep you actively updated for when your specific instance will be back available :) Ste

Hi @Vitaliy Antonov Just to clarify, why are you looking to do it this way - rather than just using the relevant Actions? It would be simpler to use the Actions... * Edit Issue: * Reviewer = {{initiator}} * Manage Watchers:* {{initiator}} Ste

Hi @Loris Garrigo Deletion is permanent in Trello - that's why when deleting a checklist it provides this warning... Deleting a checklist is permanent and there is no way to get it back. ...and requires you to double-confirm your choice to delete it. You can certainly try contacting Trello Support from this help page - but…

Hi @Shailesh Srivastava This isn't possible natively using Validators - you'd need to look for an App which can enrich the Validators on offer, allowing for If/Else rules, etc. There's a range of good Workflow Apps which have these types of extensions - see these listed on the Marketplace. There are alternatives though!…

Hi @[deleted] Is this for two Cloud instances? If yes, check out these instructions as a good starting point for Cloud-to-Cloud migrations: https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/ Ste

Hi @[deleted] A default value is just at creation. But, you have a few options to meet the above need: * Required: Make the field required, so it cannot be blank. See how to do this on this help page * Automation: Use Automation to populate the field if it's blank. For example your rule might be...* Trigger: Field Value…

Hi @Uma Subramanian There is an active incident at present - please see the Status Page for more details: https://status.atlassian.com/ I'd also consider raising a ticket with Support - https://support.atlassian.com/ - so they can keep you actively updated for when your specific instance will be back available :) Ste

Hi @Valeria Khliustina There is an active incident at present - please see the Status Page for more details: https://status.atlassian.com/ I'd also consider raising a ticket with Support - https://support.atlassian.com/ - so they can keep you actively updated for when your specific instance will be back available :) Ste

Hi @Bruce deBouver There is an active incident for Confluence - please see: https://confluence.status.atlassian.com/ for more information. Ste

Hi @Gefrey Manohar Can you clarify the relationship for more specific instructions - is it... * A parent Task, with a child Sub-task? * An Epic, with a child Task? * A custom parental relationship, using the hierarchical levels in Advanced Roadmaps? Please also confirm if... * The Project is Team-managed or Company-managed…

Hi @José Franco Can you clarify - when you say you've moved the structure but not the content, what does this mean? What did you move across? Ste

Hi @Steven Lees-Smith There's a few things I take into account when asked for very detailed forms... * User Experience: Whilst it might benefit an engineer to have all this information, the customer needs to fill it in. If the form is too complex or detailed, you might find they either don't use it - or you end up with…

Hi @Nicki D Can I clarify you need... * All Epics where the Status Category = In Progress * All the child issues of those Epics, regardless of Status If yes, I would probably use the labels approach - but I'd use Automation to add/remove labels - for example... * Add a Label to an Epic and all its children when "In…

Hi @Steve Abrahall As I said above, reaching out to Support or the Migration team is probably a next best step. Assuming you are on Server now - an alternative is to migrate to Data Center, which is still self-managed? See more information here: https://www.atlassian.com/enterprise/data-center Ste

Hi @Christian Holton A few separate questions here! I'm assuming you can use most Jira functionality for the below. Let us know if this is not the case. Identify Staff Member You mention setting the field type to single or multiple users - does this suggest a visitor could choose one or multiple employees to visit on the…

Hi @Gerardo Di Giuseppe Just for clarity, there are two types of Roadmaps... * Basic: This is available from your Board in the left-hand menu. Basic Roadmaps only show Epic and Story-level. * Advanced: This is a Jira Premium feature, and Roadmaps can be created via Plans > Create Plan from the main navigation menu…

Hi @JD Lobue I would split Sub-tasks from the filter for Standard Issue Types - so filter would be... project = ABC AND (issuetype = Sub-task OR ("Epic Link" != ABC-123 OR "Epic Link" is EMPTY)) Ste

Hi Rob, My workaround isn't an option? Ste

Hi @Carlos Giovanny Quintana Corredor I would recommend contacting either... * Another member of your team internally, who has Partner access, for assistance * Your Partner Manager * Contact Atlassian via https://support.atlassian.com/ Or, if you're not already a Solutions Partner - see this page for more…

Hi @KS Rajagopal Does it still not work if you go to... * Plans > View all plans * Select the Plan If not - what happens? Is there an error message? Does anyone have access to the Plan? If yes, and they have edit permissions, I'd get them to check your permissions... * Next to the Plan's name, go to 3-dots icon > Configure…

Hi @Amir Baruch You can see a roll-up of some data... * On your Plan - go to View Settings * From this drop-down - you can select to visualise a roll-up of...* Dates - Show a roll-up of dates in the fields and timeline sections. * Others - Show a roll-up of sprints, releases, teams, and estimates in the fields section. If…

Hi @JayJuan Jones I tested this - and this worked for me... * Condition: Advanced Compare Condition* First Value: {{reporter.emailAddress}} * Condition: does not equal * Second Value: <<email address here>> This method wouldn't need the action Add value to audit log - it should just work in place of your existing…

Hi @D L How your account works within Community, and options for association of history, can be found on this article. Ste

Hi @maria.quintana This should work... * First Value: {{issue.customfield_10155.child.value}} * Condition: contains regular expression * Second Value: (Broken light switch|Emergency lights not working) ^ I tested this on our instance, and it worked fine :) Ste