Walter Buggenhout Community Champion

Hi @[deleted], Have a look at the import configuration of the account you imported the issues into and check out the custom fields settings. It seems as if the category custom field is not being imported. Locate the category field there and import it as a Dimension. If that goes well, the dimension should appear…

Hi @Jean Ann Harrison, It is tough to build a business case for or against tools if you don't know the why for any side of the story. I would not focus on how long it would take to migrate before you're in the clear on why your IT Director wants to get rid of Jira. I know this is an Atlassian forum, but I can assure you I…

These are all ceremonies, but you can call them meetings if you like. In a retrospective, you come together with your whole team to discuss how the last sprint went, in an attempt to learn lessons from what went good, not so good or even terribly wrong during the sprint. In a daily standup, you get the team together…

Not sure if I can come up with a good one for every post, but it's worth a try 🙈

Reducing the number of users may indeed have an impact on what your are paying (if you are billed based on actual number of users at the end of the month), but it may be cleaner to downgrade or cancel your subscription as described in this support article. It also mentions what happens exactly when you downgrade. 

Hi @Marian Noorthoek and welcome to the Community! If you have imported the data from Trello into Jira and if you can see all the cards you had in Trello as issues in Jira, stopping Trello should not impact the data you have in Jira. They are different tools with a different database. If you are still working in both tools…

Hi @Scott Gillespie, The sprint report is pre-prepared and has a fixed lay-out. However, it is not at all difficult to pull a list of all stories in a sprint. Navigate to Filters > Advanced Search and just enter the following JQL: Sprint = <your sprint> It has all the issues in it. A caveat is that the issue status is…

Mission accepted @Saralie S. and accomplished: this week's Cheers for the team is out in the open!

Hi @Antun Štefančić, There is a difference between estimation and duration. It is best to use estimation as the actual amount of work you think you will be investing to get work done. This is what you enter on issues. Duration is how long it will take to complete work. This is usually longer than the actual hours being…

Hi @Mayur Gaikwad/Tech PMO, That should indeed be possible with the filter subscription approach (or automation). It's just a matter of adapting the JQL query to fit your needs. Suppose the timer you are talking about starts when an issue changes to In Progress and should be completed within 1 day, the following should…

Hi @Kim P, To quote the Agile Manifesto : Working software over comprehensive documentation. Relating this to best practice: Jira's core function is to help you plan and track your work. Not to generate release notes, although it's a nice added benefit that you can do so. For proper tracking of work: if you identify the…

Hi @Lloyd Bullard, Atlassian's marketplace policies are pretty straightforward and very open: if you add an app to your instance, it is billed in line with the user tier of the product you are adding it to. So basically: no, marketplace apps cannot be limited (in terms of license cost) to fewer users than the user tier of…

Hi @Boyd Hong, What you describe is not a transition - it is actually a conversion of an issue that was created as the wrong type into something else. Your screenshot comes from the move operation (which is the right way to address this type of change), but this is basically a maintenance tool intended to help you fix…

Hi @Mayur Gaikwad/Tech PMO, I would even prefer to do this using a filter subscription (see this blog post for a bit more context). If you have a user group that holds the team members involved and you build a filter like this ... Project = "Your Project" AND "Delivery Date" is empty and Assignee = currentUser() ... the…

Hi @Areski, A retrospective - if you play scrum by the book - is held at the end of every sprint. So, considering a traditional sprint is a 2-weekly iteration, that implies you have a retro every 2 weeks. A daily (standup) - as the name suggests - takes place every day. And on your final question about adding the…

Hi @Dennis Celen, This is a Jira Work Management project, that on top of that is team-managed. It seams that you have managed to find the project type that does not allow you to configure the board. I think that explains ... 

How you can set the same screen configuration and lay-out for all issue types is different between company-managed and team-managed projects.

As I mentioned, @František Vůjtek: the layout of screens is also linked to your issue types. If you change the issue type of an issue, you will see the screen layout that is linked to the new issue type. If that is not the same as the old one, you will see a lot of stuff being rearranged. Basically, if you notice the issue…

Hi @František Vůjtek, Yes. A request type is linked to an issue type. So if you change the issue type of an issue, the previously selected request type is no longer valid and it is cleared. Similarly, screens and workflows are linked to issue types as well. If you see the order of screens being updated, that is because a…

Hi @Girish Chitrashekaraiah and welcome to the Community! Can you search for two dimensional filter statistics instead? I don't believe that a 3-dimensional gadget exists. Hope this helps!

Hi @Berat Altunhan and welcome to the Community! In order to do so, you must have created your issue type centrally in Jira (under Jira Settings > Issues > Issue Types). If you did, you can then use issue type schemes to define sets of issue types that you can link to multiple projects. The caveat here is that you must…

Hi @Hitendra Chauhan, No, that is not possible. In Jira cloud, the email address uniquely identifies a user account. An account can simply not exist without an email address. When you want to migrate accounts from Data Center to cloud, you'll need to add a mail address before you'll be able to do so. Hope this helps! 

Hi @Vikas and welcome to the Community! Your analysis is 100% accurate: an issue is considered to be Done on a board when it reaches the rightmost column of the board. Regardless of your workflow, that's the way it works and there is nothing you can do to change the behaviour. Two potential workarounds may help you get…

Hi @Tehmina Aslam, You'll need to add the start of the day as well in order to restrict your search to just yesterday. Try the following instead: project = "Jeeny Reboot" AND ((created >= startOfDay(-1) AND created <= endOfDay(-1)) OR (updated >= startOfDay(-1) AND updated <= endOfDay(-1))) Hope this helps!

Hi @Shashank Gaurav, Unfortunately, there is no process for that. Atlassian marketplace pricing is very transparent: an app is always purchased and billed at the same user tier as the product you install it on. On the app's marketplace listing, you can read the following explanation (which is not specific to this app, but…

Hi @Yaron Norani, In advanced roadmaps you will indeed see issues in 1 fix version. And that should be the case, since it is a planning tool and the only thing you want to know is in what version (or PI) you will deliver it in. While there is no out of the box report (afaik) to display what issues were added / removed to a…

Hi @Eman Alfaour and welcome to the Community! Risk management is included in JSM as part of the Change Management process through the Risk Insights panel of a change: In this support article you can read more background information and what fields you need to enable it properly. Hope this helps!

Hi @Areski and welcome to the Community! To be perfectly open and honest, what you describe above does not resonate like a project management approach to me. But having said that, you describe most of the things involved to run it, which is a very decent plus! Running your project does involve people, practices and tools.…

On a side note: if you want to track baselines in the current tool, you could add 2 additional date custom fields to store the initial values, e.g. baseline start date and baseline end date. While Advanced Roadmaps will not offer graphical support to display then on the timeline, you should be able to add them to the…

Hi @Yaron Norani, In an older version of the tool, there has been a baseline feature included in the product. However, this has not returned to the current version of the product. There is a feature request for it in the backlog that you can track right here: JSWCLOUD-20495. In the meantime, we all know that any plan is…