Walter Buggenhout Community Champion

Hi @Karl Hamilton, As those issues have been part of previous sprint/s, I expect those sprints are still associated with those tickets. That's how Jira works: they have been assigned to a sprint, so that association remains. If you assign the issues to another sprint, you will see they'll have multiple values in the sprint…

Hi @Jim Stewart, From the customer's perspective, that would be the list of tickets he/she can view from the customer portal after logging in and looking into My Requests. To be exact, he/she should select Any status and Created by me to get that list. From your organisation's perspective, that would be through a filter:…

Talking about dark mode / as this is a feature still in the works (JRACLOUD-63150) - where did you get the screenshot from?

Although quite heavily disguised in dark mode, this does look like cloud to me guys. I don't see issues or boards in the menu up there. Having said that, automation should normally be on the page you showed a screenshot from, on the bottom left below Lexorank management. That could be a bug or a temporary glitch. You could…

Hi @Viktoria Lukinova, Jira is not very well suited to support this approach out of the box. Board columns are mapped to statuses and unless you create a workflow with statuses like To do / Monday / Tuesday / Wednesday / Thursday / Friday / Done you wouldn't be able to use a board for this purpose. If you want to use due…

Hi @Thomas Clavier, You'll need to apply for a Community license through this request form.

Hi @thijsdevries, afaik you can not install updates released after the end date of your paid maintenance. Installing a bug fix release - even on a Long Term Support release is an upgrade of your instance, as described Security bugfix policy. Maybe you already found this overview page on Long Term Support releases as well.

Ok. That may be due to a number of reasons. I don't see your data, so let me just raise a couple of options you can check: * It may be a resolved issue (unlikely if you say it's still on the board). In that case it may no longer be visible. * It may be assigned to a release that's not in your plan. * There may be a filter…

Oh, you're in advanced roadmaps! If your Epic and Story are both in the plan, you should be able to just drag your story onto the Epic.

Not as far as I know, @BT HGS. The table is generated dynamically and does not have any formatting options in that area. 

If your story is in a next-gen project, click the Add Epic button next to the issue key, at the top of your issue screen: If your story is in a classic project, you'll need to update the Epic Link field on the story. You can just fill that out if the field is on your screen, or you could drag the story onto the Epic in the…

Hi @Leo Epstein, Like most of us here on the Community, I am not working for Atlassian, but with Atlassian. So allow me not to speak on behalf of Atlassian with regards to the matter. At the same time - when speaking about Apps you are referring to a huge ecosystem. The Atlassian Marketplace is host to several thousands of…

Hi @michael_s, Tickets are visible to an organisation because they are shared with that organisation - those tickets have the organisation filled out on the ticket. So removing someone from an organisation will not impact visibility of that ticket to other members of that organisation.

Hi @Aidan Matheson, Your internal users who write the KB articles need a Confluence license. They're the ones who need to write stuff there, so they are your licensed users. Your service desk users - the folks who will be seeing KB articles through the JSM portal as they are searching for help or creating content do not…

Hi @[deleted], SQL server is supported up to SQL Server 2017. You can check the supported platforms on this page 

Hi @Tom Feist-Wilson, This is because the issues don't have a value set for Resolution. Open requests are not based on the status of your requests, but on there being a value in the resolution field. You'll have to make sure that a status transition to a done status in your workflow also fills out the resolution. That can…

Hi @scdeloach, The nature of the app is to deeply integrate content into your Confluence pages and it the makers have thought it makes more sense not to make it accessible through the apps menu, but more in context with where you work. Think of it as if you want to insert e.g. a picture in a Word document. It is more…

Hi @Alan Mathew, You can edit the Confluence themes yourself if you have the skills and resources available to do that. For more information about how to go about, have a look at working with themes documentation If you don't, the marketplace has a lot of options available to support you with that. As an entry point, have…

Hi @Leo Epstein, I'm afraid @Jack Brickey is right on this matter. I'd like to add that not all apps manipulate data - so tracking usage of those could be a question of asking users how they are using them. Since this is about migration, there's some things you could do to narrow down on the task at hand too: * First of…

Hi @Sergio Beretta, Thanks for your reply and the additional information provided. You are right that there is an issue with validating both fields of a cascading select. There used to be a feature request for fixing this: JRACLOUD-10302. Atlassian has acknowledged this being an issue, but also indicated that it has no…

Hi @Sergio Beretta, Welcome to the Community, also on behalf of the many women's here ;-) Are you sure you marked the fields as required on the request type form? When you are configuring your project, in Project Settings > Request types > click through on a request type > Request form: If you mark a field as required…

Hi @Paul Gautier, This link is a more generic feature that unleashes the power of using Jira and Confluence together. You are absolutely right that this link will not be visible to the reporter like this and it is not really what it is meant for. However, Confluence can be used for a wide variety of documentation and…

Hi @Gonzalo Benitez de lugo, Unfortunately, the labels field does not support history search. If you know when the accidental update occurred, you can narrow down through a search on updated issues in that time frame: updated >= date1 and updated <= date 2 and labels is empty On the history tab of each issue you will be…

Even CEOs sometimes invent tasks for a reason, you know ;-) That left aside: yes you have all the data, you have Tempo to pull reports that give you some, but not all level of detail, so you do have gaps to fill. So you'll need to work on closing those gaps anyway. You could build a spreadsheet template that holds your…

Then another reporting solution might be the answer. Yet - I get the impression that there is something you need to do on a weekly basis and you've come to the conclusion that this report is your answer to that problem. What problem are you trying to solve?

Hi @Padmakanta Parida, If it gets assigned to someone else when a story is closed, that is most likely because there is a post function in your workflow responsible for this. Fixing this is basically very simple: * Edit the story workflow of your project; * Locate the post functions associated with the close issue…

Hi @Feliks Dzhegutanov, Assuming you do have Tempo Timesheets already, you can create reports for the individual teams (filter by instead of group by) which you them group by project. In my mind it's then a fairly small step to export / copy-paste those data into a spreadsheet like you did to illustrate your question. It…

Hi @Aishwarya Rajendra, Cloud and server are different products and may/do differ in behaviour. Reference the Cloud documentation which does not have the same level of refinement as on server instead. So in short: the server documentation does not apply to cloud.

Hi @Sam Hoover, Check the Transition issues permission of your project through Project settings > Permissions. If you are an administrator, you can also check what's going on with the Permission helper. Type g+g on your keyboard and in the dialog box that pops up, type permission helper. In the screen that appears, enter…

Hi @Jordan Nussbaum, Jira has a built-in field called Workratio, which calculates the percentage of time spent vs original estimate. You can build any filter and include that field in the results: I don't have much data in my test instance, but I hope you get the idea. You can use workratio in your filters as well to…