Ste Wright Community Champion

Comments

  • And in Korean (according to Google Translate)... --- 인스턴스와 조직을 직접 삭제할 수 있습니다. 제품 * https://admin.atlassian.com/으로 이동합니다. * 청구 탭으로 이동합니다. * 제품 옆의 "관리"를 선택하십시오. * 다음으로 각 제품의 이동 경로(점 3개 아이콘)를 선택합니다("사용자 관리" 버튼 옆). * "삭제"를 선택하십시오 * 지침에 따라 각 제품을 삭제하십시오. --- 조직: 이 도움말 페이지에는 몇 가지 전제 조건을 포함하여 이에 대한 몇 가지 지침이 있습니다…
  • Hi @양세윤 You can delete your instance and organisation directly. Instance: * Go to https://admin.atlassian.com/ * Go to the Billing tab * Select "Manage" next to any product * Next, select the breadcrumbs (3-dots icon) on each product (next to "manage users" button) * Select "Delete" * Follow the instructions to delete each…
  • Hi @[deleted] Almost like a repeat of the Releases Hub for official versioning? You could... * Use a gadget to summarise the "releases" list, like a Two Dimensional Filter Statistics gadget * List the issues per release in multiple Filter Results gadgets ^ This isn't quite what you need, but it's a potential alternative.…
  • Hi @Jagmohan The Action you need is "Edit Issue" You can then select the field "Fix version", and set it from here. Ste
  • Hi @Marco Ferra Not natively - search lists the results of the actual query, one row per issue - it can't be setup to show the data in your required format. What's the need you're trying to fulfil? There might be an alternative option for visualising the data in this manner. Ste
  • Hi @Gareth Blake-Coggins It does say this... Consolidate tools with a digital whiteboard at no extra cost. Confluence whiteboards is always included with Confluence ...on this page: https://www.atlassian.com/software/confluence/whiteboards And then, in the FAQ (further down that page)... How much does Confluence…
  • Hi @Hollee Are the fields on just the Epic and the direct children? Or the Initiative also? And are you doing a multi-Project rule (via Global System Settings) - to copy data between two Projects in this manner it would have to be a multi-Project or Global rule. Ste
  • Hi @Karoly_Tanczos Strange! I'd contact Atlassian for this one, via: https://support.atlassian.com/ Ste
  • Hi @David Leal I feel like it'd be best to review your rules, it feels like they're conflicting with each other. For Rule 2, I think you'd also need to edit the "For" section of the trigger to not include "Create Issue", otherwise it still won't be reacting to the "Allow rule trigger", it'll be running in parallel with…
  • Hi @Rahul So it should be possible using IF/ELSE via an Automation rule - for example: * Trigger: Issue Created * Condition: IF Block* IF...* Condition: Issue Fields Condition* Field = Affects versions * Condition = equals (in any order) * Value = Version 1 * Action: Edit Issue* Field = Fix versions* Value = Version 1.1 *…
  • Hi @Ian Brown This isn't possible natively I'm afraid. You could move across to a Jira Software Project, this allows Sub-tasks to be moved across the board itself, so you could move them to "Done" as they're completed. Or from within Jira Work Management, you can click on a Task to view the detail either as an iFrame…
  • Hi @Jennifer Ramey I don't see any images, could you attach them directly from within the Community? I modified your post to remove the email component, including your email address, as this is a public forum and didn't think you'd want it visible to everyone :) Ste
  • Hi @Cindy Beyer Is that happening for all users and on all browsers? I tested this on Google Chrome and the Story opens whether I'm using the Assignee filters or not. If it's widespread within your company, I'd recommend contacting Atlassian directly for more support, via: https://support.atlassian.com/ Ste
  • Hi @Lydia M Browse Projects is only controlled through Permission Schemes, there's no global setting for this. That means existing Projects have provided access beyond your need and/or your Permission Scheme isn't set up as required. Could you provide a screenshot of your "Project permissions" (just the top section)? ---…
  • Hi @Lori Gipp I've seen teams do this in the past - it's setup like this... * Kanban Board: Creation > Ready (including Sprint Ready) - the board is used for initial scoping, story writing, bug testing, etc. * Scrum/Kanban Board: Ready > Done. Utilises a backlog, where items aren't added until they're "Ready" In effect,…
  • Hi @Barış Özer The workflow condition model comes with some caveats: * You might need to have workflow transitions be closed - because otherwise a user could "avoid" the approval step. This means no all <> all transitions * You might be able to mitigate that using "Previous Status" conditions, but I think it'd get quite…
  • Hi @Brad Rutledge Epic Name isn't a field at Story level - are you trying to add the Epic Link (i.e the parent) to each Story you're importing? If yes, you'll need to map the Epic issue keys to the Epic Link field, which should then work :) Ste
  • Hi @Lalithesh Has the other error cleared up now? For the other requirement, an Advanced Compare Condition would be able to check how many comments an issue has (in general) - this should work: * First Value = {{comments.size}} * Condition = Equals * Second Value = 1 ^ But this isn't per author. Is this sufficient? Ste
  • Hi @Quang Nguyen Is that user a licensed member of Jira for your company? Ste
  • Hi @Rob McBride Interesting - but does this user class as a Service license? The "Customer" role should not increase your license usage, only "Agent" Check license usage via the Billing tab Ste
  • Hi @[deleted] Yes - for any Project which doesn't use all the resolutions, the transition properties are needed. You should enter the IDs without spaces in the transition properties. --- To give an example of how to do this: * Go to Settings > Issues * Select Workflows from the left-hand menu * Locate your Workflow, and…
  • Hi @Gerard Cattin You should be able to do this using two separate rules - which are: * Copy FixVersions from Parent, when the Versions change, and... * Set FixVersions in newly created Sub-tasks from the Parent ^ This covers all basic scenarios I think. --- Rule 1: * Trigger: Field Value Changed* Field = Fix versions *…
  • Team-managed isn't the same as a Company-managed Project. In Company-Managed, a status controls whether the issue is on the Backlog or on the Board - it's like an additional column in a separate tab. In Team-managed, the Backlog and Board are two separate entities - they're not status related. You'd need to drag/move/send…
  • Hi @Héctor Fenoll Malonda I've seen your previous question here, and will alert Atlassian in relation to this. Ste
  • Hi @Jack Tucker I locate it from the URL, by editing the sub-option in the cascade field options You can see it here: * ParentOptionId=10123 - primary option ID * selectedValue=10124 - sub-option ID I can't always see the full URL by hovering over the "Edit" hyperlink, so I open the edit link in a new tab. I assume it's…
  • Hi @Martin Hirsch With the backlog activated, new Issues are created at the bottom of the backlog, rather than directly on the board - are they not there either? The backlog is on a separate tab, you can access it from the left-hand Project menu, between the Timeline and Board options. Ste
  • Hi @samuel_cherry You'd need a Jira Admin to make these changes - often they work for your IT Services team or similar. Ste
  • @Jack Brickey * https://bugs.mojang.com/projects/MC/issues/MC-240966?filter=allopenissues * https://bugs.mojang.com/projects/MCPE/issues/MCPE-173806?filter=allopenissues Ste
  • Hi @[deleted] Yes, if you add a resolution and do nothing else, everyone will receive the full list. You'd need to limit resolutions per Workflow to show a smaller list for other Projects - you can do this using transition properties. These are: * jira.field.resolution.include * jira.field.resolution.exclude For more…