Walter Buggenhout Community Champion

Hi @Victoria Ayisi, What others have said about the definition of "a scrum job" is true. But - assuming you are hinting about a role as scrum master or product owner or something like that - it is totally normal that experience is a requirement. Those are responsible roles for leading a team, making key decisions about a…

Hi folks, I have a long history in the Atlassian world, going back to 2011 when I joined my current company as the PM of a Software team. As I joined our Atlassian business unit in 2015, I was just in time to see the birth of Jira Service Desk as a separate member of the Jira family, growing from the add-on it initially…

Hi @James Carn, Even though Jira Software Premium does offer unlimited file storage, I would never think of Jira as your weapon of choice for large file storage / file management. Can't you store your installation files on a solid file storage system and add links to those files in Jira / Insight instead? 

Hi @Ole William Hansen, It is indeed not so much your automation rule, but the mere fact that you mention users on the ticket that triggers this behaviour. As you can read in the documentation, mentioning users does automatically add them to the ticket as request participants. This is by design, as the underlying…

Hi @Belem Acosta Rascon, Whilst I am not familiar with your setup, these templates are not standard Jira and thus provided by a marketplace app. The first thing I would do, is make sure the license of that marketplace app hasn't expired, as that would disable the app's functionality. With Jira Admin rights, you can check…

Hi @JP Woodbridge an welcome to the Community, I would assume that you have set up your SLA in such a way that your SLA timer gets paused when a ticket enters the Waiting for Customer status. So you can best uses history search in JQL to trigger your automation. On top of that, we have sometimes introduced a custom field…

Hi all, As many here before me, I am not really new to Jira anymore. I started using Jira back in 2011 to plan and track the work of the development team I worked for as a business analyst and Proxy to our customer(s). A lot happened since. I've seen Jira split up in Jira Software, Service Management and Core (now Work…

Hi @Derek Crawford, You are very rightfully referring to a well-known issue, that is captured in JSDCLOUD-5878. The good news there is that a fix appears to be currently in development and is expected to be released somewhere during Q4 2021. I recommend you to watch that ticket for further updates. 

Hi @Jessica.D.Pennell, I believe your request is related to the Xray product, which is developed by XBlend. I think you can best address your request directly to them through their support channels. You can find more details on the app's marketplace listing.

Thx for jumping in on this one, @Angélica Luz! 

Hi @FAsmani, You could create a dashboard and add these gadgets: * Sprint Health Gadget * Days Remaining In Sprint Gadget * Sprint Burndown gadget You can configure which board and sprint you want them to use. And I think they will nicely present all the information you are looking for. Hope this helps! 

Well searched, @Alex - I had looked for feature suggestions too,, but not with a lot of success 🥇

Hey @David Wuth, Aha, yes - you could be right that I'm wrong 😇. It appears that advanced roadmaps does indeed have its own ranking system now. Quite complex stuff, apparently. Did you have a look at the documentation on ranking issues? There's quite a few factors that impact behaviour, so it seems worth diving into the…

Hi @David Wuth, I have looked through both the documentation and all the permission settings I can find and I am afraid this is not possible currently. It seems that the people with edit permissions on a plan also have the power to modify and save changes to views.

Hi @David Wuth, The thing is that this ranking thing is not relative - it is pretty absolute. Essentially the ranking is a central concept behind the scenes that ranks literally all issues in Jira. Every issue has its own position in the list. And if you update that ranking (no matter how), you update the issue's position…

Hi @Christian Neubauer, To change the hierarchy configuration itself, you'll need to navigate to <yoursite>.atlassian.net/secure/PortfolioHierarchy.jspa where you can introduce new levels or remove old ones. You can drag and drop the levels above Epics in the order you want. Have a look at this support article for a more…

Definitely interested and looking forward to providing feedback!

Hi @CHESTER RAMOS, It seems you are overcomplicating things here. To make your automation rule work, just enter "Employee ID" in the Value section of the condition: On a side note, I would recommend you to use a more structured way to organise your types of work than depending on text being entered in the issue summary.…

Hi @Baris Sehitoglu, Custom fields in Jira have a context. It allows you to configure different behaviours of your field depending on the project(s) or issue type(s) they appear on. It is possible to configure multiple contexts for a single custom field and that includes showing different options to your users. Take a look…

Hi @Amber Field, You can still find renewal pricing in the licensing faq. As @Robert Wen_Cprime_ explains, it remains possible to renew maintenance until February 2nd, 2024. One thing to keep in mind is that from February 2nd, 2022, you will no longer be able to upgrade/downgrade to a different user tier.

Hey @Phillip Traynor , Yes, if you can't set the customer request type on your csv import, you can bulk update the imported issues after the import to complete the missing data. Furthermore, if you want to hide the request type from the portal, all you have to do is make sure that it isn't added to any portal group:

Yes, it is on the screenshot I shared: status = resolved and status was resolved before -7d

Hi @Chris Riddle , There's a couple of things to ensure: * In project settings, look for screens and locate the screen(s) associated with sub-tasks. Make sure that the due date custom field is present on those screens. * In the same project settings, check the issue layout and make sure due date is visible there as well. *…

Hi @Sergio Yelamos Jimenez and welcome to the community, Something like this should do what you are looking for: I used a combination of search on current status and what the status was more than 7 days ago to trigger the rule. You can find a good article on history searches right here if you want to learn more. Hope this…

Hi @Michael Heilig , If you are logging hours using the standard Jira features, the following should work: timespent > 40h Of course you can combine the above with additional criteria, such as the project the issues are in.

Hi @Phillip Traynor , It is very well possible that the customer request type is not filled out on the issue. If that is the case, issues won't be visible in the portal indeed. Hope this helps!

Hi @Anamika Sharma , If you use the built in Original Estimate / Time Spent (Time tracking) fields in Jira, there is a standard feature you can use for this. There is a default field called workratio that does exactly this calculation for you. You can even use that field in JQL to search for issues where the actual time…

Hi @David and welcome to the community, What you are trying to do is not possible in Jira. Versions do not have a hierarchy. A common practice for technical releases is just use a naming convention that you would also use in the product you are developing itself. * 1.0 would then be a major release (e.g a platform…

Hi @Amirhossein fathollahi madani , The scenario you describe is usually a process where part of the workflow (initial scoping and analysis) is done by e.g an analyst, PM or PO and then from a certain point in the process, those same issues are handed over to development through a status transition in the workflow. That is…

Hi @Anton Prokopenko and welcome to the community! The dates indeed don't go beyond 2023 and you can't extend that range apparently. As a workaround, however, you can fill out the start and end dates for your Epics in the following custom fields: * Start date: represents the start of your epic * Due date: represents the…