Ste Wright Community Champion

Hi @Laura Spencer Given the issues mentioned here - especially around Plans not loading - I would suggest you contact https://support.atlassian.com/ for more assistance. Support will be better placed to investigate what the issue might be. Ste

Hi @Linda Ouzerout This works for me; when I enter text into this search box it will list issues available with those words (in order) in the Summary. What happens as you type text into the box? Ste

Hi @Daniel Bieńkowski The error is caused by this part of your JQL: "Epic Teams [Checkboxes]" = "Team 1" Because the master project is not defined in the query, Jira is assuming the issues could come from any project, so requires a user who is managing sprints to have the permission in all projects. But even if you refine…

Hi @Rajiv Ranjan Check out: How to limit editing permission, to certain groups, for a particular Issue Status Is this what you were looking to achieve? Ste

Hi @darren.lee You can from the reporting page: * Go to Reports * Select the Sprint Burndown Chart * Select the desired sprint from the field near the top * Next, scroll down past the chart to the bottom of the page At the bottom is a summary of issues which were completed vs incomplete vs completed outside the sprint. Ste

Hi @akovalevskaya Issues which have been resolved for more than 14 days are removed from the "Done" column automatically. These issues are still possible to locate via issue search or the issue navigator (if this Feature is activated for your project), but won't be visible on the board. Ste

Hi @darren.lee In Next-Gen, yes - only one sprint can run at a time. This won't happen to Sprint 3 as long as when you complete issues in Sprint 2, you drag them into the "Done" column at the furthest right-hand side of your Board. Completed issues are not returned to future sprints / the backlog when the sprint is closed.…

Hi @[deleted] I think this is down to how you define your metrics and ways of working. In an ideal world, a card will move left-to-right - flowing forward through each status. But not every issue moves forward without error. If testing fails - you could either: * Leave the issue where it is - and have bugs or errors fixed…

Hi @darren.lee It looks like you had already completed Sprint 1 before Sprint 2 commenced. If so, it is not possible to reopen, edit or delete a closed sprint in Next-Gen - vote/follow JSWCLOUD-17208 if you are interested in this functionality. Your options here are: * Continue with these issues in Sprint 2 or... * Remove…

Hi @darren.lee It is on this Board view that Done has to be the furthest-right column. At present "Done" is in the middle based on this screenshot - if you click on the column header you can drag "Done" to the right-hand side (past all the other statuses). You might also want to reorder or delete some statuses in general -…

Hi @darren.lee Just to clarify @Alexis Robert's comment, the tab will be called "Board", as this is a Next-Gen project. We need to see the board view where there are columns which represent statuses :) Ste

Hi @Sebastian Krzyzanowski The latter part of the rule will never activate. This is because the original conditions will prevent issues from passing forward down to the second set of conditions / actions. However, you could break the rule into two separate branches, which can operate similar to If/Else for related issues.…

Hi @darren.lee I'm not sure I understand how the last column is Assignee. Could you provide a screenshot of your board, specifically the last few columns which show "Done" and "Assignee"? Could you also explain what the purpose of the Assignee column is? Ste

Hi @Kasper Post The first rule might look something like this: * Trigger: Issue Created * Condition: Issue Fields Condition - Issue Type (field) equals (condition) Bug (value) * Condition: Issue Fields Condition - Description (field) contains (condition) {KIM1} (value) * Action: Edit Issue - choose to set Components to…

Hi @Alan Tan On the old view, time tracking will not appear on the view screen unless one of the fields is populated. To set the original estimate: * The field Time tracking needs to be available on the issue's edit screen (not issue layout, which is related to the new view) * Your colleague will need to edit the issue You…

Hi @Scott Harman Restricting comment visibility is not available in Next-Gen projects at this stage. It has been suggested though, vote/follow JSWCLOUD-18778 You can limit comment visibility in Classic projects, as an alternative. When adding a comment, there will be a padlock icon in-line with the Save button, in the…

Hi @Amen GALLEY You mention in Product Plan you're on a Free version of Jira. In Free, changes to permission schemes are restricted and are not configurable, so all users can see all projects by default. Read more about permissions in Free plans on this page. You'll need to upgrade to Standard or Premium to take advantage…

Hi @darren.lee To be classed as "Done" the issues need to remain in the Done column (or the column which is signified as completed based on the green tick). It then needs to be in the last column on the board to be classed as "sprint done" from a reporting perspective. So that your issue is resolved and it is correct in…

Hi @darren.lee I assume this is a Next-Gen project, based on the workflow editor? If so, if "Done" is classed as completion, it should have a green tick in the column header, to signify this. It's worth confirming that is there. "Done" should ideally be the last column on the board itself - if it isn't: * Go to your board,…

Hi @Danielle Silva There's no specific method to keep a columns status(es) visible at all times. If you are using a Classic project/board, you could rename the columns on a board to reflect the status names (especially if you have one status per column). To rename columns: * On your board, go to the breadcrumbs (...) in…

Hi @Mac McCabe You should be able to locate the correct field parameters from viewing an Epic's issue details. You could use: * https://<instance name>.atlassian.net/rest/api/2/issue/<issue key> - to view field name / ID mapped to values * https://<instance name>.atlassian.net/rest/api/2/issue/<issue key>?expand=names - to…

Hi @[deleted] Can you share an example of the JQL you used, with the function above? Ste

Hi @sanjay_sapra I'm not sure if this will fulfil your needs, but you could check out Workflow Rules Lite which I found on the Marketplace. Alternatively, you can search the Marketplace for other free apps. After searching for keywords, choose to only show "Free" results from the left-hand Filter By menu. Ste

Hi @Leo Epstein This is a restricted action in Cloud. It has been suggested to change this, although the main suggestion - JRACLOUD-7266 - is closed as "Won't Fix". Some alternative options are: * App: An app which can help with notification customisation, such as Enterprise Mail Handler for Jira or Raley Email…

Hi @Ron Chipman I know it isn't possible simply - it is a suggested feature, vote/follow JRACLOUD-74105 You can also check out JSWCLOUD-19451, which suggests allowing Parent Link to behave like Epic Link I haven't been able to locate a method to do this. You could create an additional link (via linked issues) between the…

Hi @sathis kumar Sourcetree is a free product; it's a free Git client for Windows and Mac. See more about Sourcetree and downloading it from this page. Ste

Hi @Hugo Godinho This answer suggests this might be possible. I would check out: * Atlassian Cloud: Authentication * Cloud Identity and Access Governance * Configure user provisioning for Active Directory * User Provisioning These pages mention what is needed/available, and what additional products you might require in…

Hi @Muhammad Faisal What error are you receiving? Just to confirm, if this is Jira Cloud there is a 10 user limit - but if this is Jira Service Management, there is a 3 agent limit. You might have gone over your agent limit in this instance. See more on Free product limits on this page. Ste

Hi @Gaurav Rajpal There's some great information on this in these pages: Set up authentication for Statuspage users I'd check these out first to see if they help with your queries! Ste

Hi @Anca Huruiala You should be able to create multiple future sprints in a Next-Gen backlog. In line with the Backlog section, you should find a button - Create Sprint - on the right-hand side. If you mean parallel sprints (running two active sprints concurrently), then this is only possible in Classic Projects with the…