Ste Wright Community Champion

Hi @thomas.hargreaves I haven't seen one tool or app that does all those things. There might apps that do some of this - such as Instance Auditor (Jira) - but aside from that, like you I would probably utilise the API and/or custom searches/dashboards to locate the rest of the information. Ste

Hi @Kmmaughs I'm not sure how to do it via Post Functions - but it might be possible via Automation? It looks like you need: * When ABC-1 is transitioned from Status A to Status B, create ABC-2 and link it to ABC-1 * When ABC-2 is closed, create ABC-3 - and link it to ABC-1 * Stop ABC-1 from being closed if ABC-2 / ABC-3…

Hi @Srilata Meka You need a field to display the issue age first, to then visualise this data on a dashboard gadget. I've found a method to do this using Automation for Jira. -------------- To do this, as a Jira Admin: * Go to Jira Settings > Issues > Custom Fields * Press the blue "Create Custom Field" button in the…

Hi @Sapna Mogili That seems strange - I agree with @Carlos Garcia Navarro that the field shows as "None" on the dashboard - whether it is multi-user or single-user. It looks like this is a known bug though for all gadgets - see JRACLOUD-72205. You can vote/follow it to track its progress. In the meantime you might need to…

Hi @Michael Arndt Yes - so this is where you'd use Bulk Change. You will need: * Global Permission: Make Bulk Changes * Project Permission: Transition Issues - and possibly, Resolve Issues / Close Issues. Or if this is Next-Gen, at least the role - required per project an issue is within ------------------- Then, follow…

Hi @Michael Arndt It depends what you want to do with them. You could: * Move: Place all the stagnant issues into one project. Then, give the project its own permission scheme and give no-one the permission "Browse Projects" - effectively hiding the issues from all users. * Close: If the issues are stagnant but still need…

Hi @Jacob You can't modify the base Jira URL on a Cloud instance at this stage - you'll need to create a new instance then migrate your data across to it. See this page for more information and instructions on how to do this. Ste

Hi @Ksenia Abdulina I don't have this app - but just a guess based on their Marketplace listing - try: * Removing the Description and just including the colour in brackets or... * Placing the colour above the description If you want to include both a description and the colour and the above doesn't work - I'd suggest…

Hi @Josep Canet I don't believe this is possible at this stage with tables. You can press Shift + Enter to add a line below a number and enter additional text - but if you try to add a table, it just creates it below the last numbered row (in the new editor) or greys-out the create option (in the legacy editor) You can…

Hi @daniel What error do you receive when you try to use your current email? Not sure what you mean by "Project Manager" account - but you can modify the email address associated with your own Atlassian account: * In Jira, go to your user icon (top-right corner) * From the drop-down, select "Account Settings" * Select…

Hi @Roland Illig I don't believe there is one. Most regularly, I see teams having more than one instance for this. For example, a Test instance and a Production instance. That way you can upgrade your Test instance and ensure it doesn't break anything before making the upgrades in Production. I'd see if your Administrators…

Hi @[deleted] To confirm, do you need to see: * Features & Stories which are blocking each other, either in FPM or another project * Stories from other projects which are blocking FPM stories Let us know as this might require an app to extend the functionality of JQL to allow you to do sub-queries within a main query.…

Hi @Ksenia Arkhipova It might be possible via Application Links. But I'd advise contacting the vendor directly to seek their advice - they'll likely have the most experience in this! You can see options to contact the vendor on their Marketplace support page. Ste

Hi @Amit Anand Can I confirm the need here: * If Project 1 has at least one bug, Work can contain "PROJ" * If Project 2 has at least one Task, Work can contain "SUP" * If Project 1 has at least one bug AND Project 2 has at least one Task, Work can contain "OTH" Is this your need? Is the field "Work" on each project or on…

Hi @fahad.niazi This should be possible in Automation - to access Automation at a project-level, you'll need to be a Project Admin and then: * Go to Project Settings > Automation * Press the blue "Create Rule" button in the top-right corner to start ------------ For the rule, use this: * Trigger: Issue Transitioned - To…

No worries - let us know if it works! Ste

Hi @Vivian.HOAREAU First thing to check - on the rule itself, the Trigger states when issue transitioned FROM Done, Closed. This should be TO as you're closing the issues, not reopening them. I'd fix this first and see if it works. --------------- If this doesn't solve the issue... Are there any properties required to move…

Hi @Herbert Kevin This is available in Server/DC - see this page for confirmation. So a search such as all Versions which begin with "Ver" would be: affectedVersion ~ "Ver*" ------------------- This isn't available in Cloud - in this instance, you'll need a JQL extension app, such as ScriptRunner. For example, using…

Hi @Sapna Mogili Awesome - give it a go and let us know if it works! Ste

Hi @Sona Evanesyan You could do this using Automation. To create this on a project-level, you'll need to be a Project Admin and then... * Go to Project Settings > Automation * Press the blue "Create Rule" in the top-right * For the Trigger, use "Issue Created" * Add an Action, use "Edit Issue" - choose to set the…

Hi @Mark Grenville All issue types in Next-Gen products share the same workflow at this stage - so whatever workflow is configured on the board will also be shared with Epics. If you are referring to the drop-down filter "Status" in the Roadmap view - which includes To Do, In Progress and Done - this is just filtering on…

Hi @Mark Grenville Not natively - each Next-Gen project is entirely independent and you need to create fields, etc in each project individually. There are a few suggestions you can vote/follow for this, such as JSWCLOUD-17430 Or to see all current suggestions for Next-Gen - which you can search to see if one closely…

Hi @MarcoSoft PE Is this for Atlassian Cloud? If yes, you'll need to be an Org & Site Admin and then... * Go to https://admin.atlassian.com/ * Select your Org * Under Site, select your site * On the left-hand side, select "Manage Subscriptions" * On a product card, select the breadcrumbs (3-dots icon) in the bottom-right…

Hi @Roger Hancock You can do this: * Go to the the single issue you wish to link multiple issues to * Press More > Link * Select the appropriate link type * Either enter the multiple issues one at a time into the "Issue" field - or... * Select the hyperlink "Search for an issue". On the next page, select "Advanced Search"…

Hi @Dinu Radian I ran through your scenarios. I've clarified each scenario just to confirm we're doing it the same way. ---------------- Scenario A: * Went to Projects > Selected a Project * On the left-hand menu, selected Issues (viewing "All Issues") * Pressed the hyperlink "Advanced Search" * Changed the filter on the…

Hi @Sapna Mogili Best option I've found it to use a workaround - in this case, a custom field and an automation rule ---------------------- What I did was: * Add a custom label field to the Epic - "Epic Reference" * Populate the "Epic Reference" for each Epic with a short name (manually) * Add the same field to each child…

Hi @Nguyen Duc Hoang Just to confirm - you're looking to... * Create a custom field or fields which are a multi-text field (or similar) that... * Would be blank at creation but required prior to an action being taken (eg. added to a sprint, moved to a specific status, etc)... * And users would populate it with data from a…

Hi @Ng, Alberto To confirm: * The "Initiative" is an issue type, configured in the hierarchy above an Epic (or similar) * You're adding the Initiative to a Plan and then... * Committed the change to Jira --------------------- If this is correct - then the Initiative will show up in any plan where it is configured to do so.…

Hi @Asher Francis I gave this a go in a test instance - and it works for me! I would check: * Permissions: All users in the team have access to see the issue - that includes "Browse Projects" permission in the permission scheme, and the "Service Desk Team" project role (esp. if they're not an agent and just need observe…

Hi @Larry Katz To confirm: * There is one issue per release of type "Release Candidate" * RC has a FixVersion, unique to it * If Bugs, Stories or Tasks have the same FixVersion added to it - they should auto-link to the RC issue ------------------ If yes, this is how I got it to work: * Trigger: Field Value Changed -…