Walter Buggenhout Community Champion

Hi @Khawaja Adeel, If you make the QA step an integrated part of your workflow, there is no reason to create duplicate tickets. You just update the ticket status to QA (you may even use a post function or an automation to update the assignee automatically as part of the status update) and make sure your QA people can…

Hi @Dar Kronenblum, I'm not entirely sure what you are trying to achieve, but you don't need an API to publish events in Jira itself. Triggering custom events from within Jira Cloud is built in. Maybe this support article is a good starting point, if you want to trigger events from workflows. Apart from that, the also…

Hi @Mohammad RahmaniNasab, There is a feature suggestion for this in the product backlog that you can track here: JSDCLOUD-4867. According to a rough estimate from March this year, it may be roughly expected by the end of this year. You can watch the ticket to stay informed of future updates. Hope this helps!

Hi @cuong_nt1, As @Jack Brickey suggests, you can't configure the list of suggestions. It may be worth noting that the field "Raise the request on behalf of" is only visible to Service Desk Agents. Customers do not see this field when raising a ticket. Maybe that may reduce any concerns you may have?

Hi @Raymond Kerckhoffs, Following up on @Dirk Ronsmans' suggestion on additional suggestions, I ran into this support article on federating Jira, managing multiple instances. While it is written with the Data Center in mind, many of what is said there, applies to cloud as well. If you can't get your data in a single view,…

Hi @Asif Zahoor and welcome to the Community! This "SAU: Issue Type / Sub Type / Element" you are referring to is something specific to your Jira instance, most likely. But to answer your question generically, I would say you can just further expand your initial JQL statement like this: Project = USD AND resolution =…

Hi @Nicole Howard, Although very short, this support article explains how you can add, rename and remove categories. You can (currently, I would suspect) only do this in list view and only if you have administrator permissions. Hope this helps! 

Hi @João Rigueiral, The admin environment does undergo changes every now and then and navigation there is sometimes influenced by that. On a test site I have, I got to the billing details through the following steps: * Log into admin.atlassian.com * Select billing from the top level menu structure * Then click manage…

Hi @scott_price, The workaround you describe is currently indeed the way to go. I suspect the main reason behind this, is that Advanced Roadmaps originally was built on the on prem platform first, where priority schemes are an existing feature. These schemes allow for different projects to use different priorities. As…

Couldn’t word it any better than @Andy Gladstone just did! This was a great exploration of community content, serving a really good cause; I also must say I loved the story behind this initiative and feel really inspired to take the spirit of it into some local cause (whatever that may become) onwards. On a final note -…

Those final updates were so funny and encouraging that I couldn’t help throwing in a couple more from a terrace in Malta 😛! We must so close 👀👀👀

You did add your issues to that sprint before you started it, @Khawaja Adeel? 

You are completely correct, @Shari Fitz-Patrick. You would create a project that represents a product. And in it, you can use components, versions, etc. If your company is building products, that would be the way I would recommend setting it up like that as well. Regarding your epics, you could either use a project…

Hi @Shari Fitz-Patrick, It depends what you mean by projects. If these are actual Jira projects, that won't work, as every issue in Jira is stored inside a project. If a project, however, is an issue type that is in your roadmap at the level above Epics, then that is a decision that you can take at your own discretion. It…

Hi @MARY USEN, The issues calendar gadget can display any date (custom) field you have in Jira. But only one at a time, as you can see from this configuration screen: So yes, you can display the due date or the target end date, but you can't show both in the same calendar. About your JQL, assuming that you want to fetch…

Apart from the initiative itself, it's really awesome to tap into the genuine inspiration behind it all. I am definitely going to take the essence of it back to my kids - currently 16 and 13 years old - and see how it may motivate them to also do something they actually can. Thanks for sharing!

You are sure you have added the issues to that sprint, right? If not, they should be in your backlog, where you can add them manually to the sprint.

Hi @Ken Collins and welcome to the Community! Moving between project types is a painful experience. It just is like that. For the Epic name, I would suggest you just fill out a hard coded value and then update the Epic names manually after the migration in your company managed project. For the acceptance criteria, I saw a…

I almost liked myself an arm off by now, but I'm proud of my contribution so far 😎. I'm leaving on holiday tomorrow, but I'm sure you guys are taking this ship tree right into the harbour forest the next couple of days! When you haven't been there yet and don't know what to like, go and appreciate this months haiku…

Hi @Craig Lambie and welcome to the Community! One wise person once said - in Latin: "de gustibus et coloribus non disputandum est" - it does not make any sense to argue about taste and colour. So, if you like colours: great! If others don't: equally great! In software and design for quite some time we take into account…

Hi @Jonathan Lowry, From your description, it seems you have your plan grouped by Project. This is essentially just a way of viewing your issues. Advanced roadmaps just displays the issues hierarchically. If you would remove the grouping, you would see the issues only once, neatly organised as parent issues with their…

Hi @Ignas Selvestravičius, As the first screenshot says: your board has no location (anymore). This may have happened because the project it was linked to was archived or deleted or the user it was associated with is not longer active. Update the board location as described in this support article. Hope this helps!

As you mentioned, @Christine P. Dela Rosa, totally agree with how taking the time and effort to pronounce one's name correctly is the least one can do to show interest in someone else: Outside of this conversation on nicknames to help us add a layer to our identities (for better hopefully), getting names pronounced right…

I'm sure you'll get to something that works for you and your team! 🚀

Thanks for sharing, @Yair! While the statuses with no linked transitions should obviously not be set up like that, they do not impact that you cannot transition away from the to do status. Most likely, the transitions from to do to In Progress and Pending Review have a condition configured that is restricting you from…

That sounds like a great idea. But as you explain it, it sounds like you are trying to automate something that is to complex to automate - possibly because you would like to capture every possible use case (or combination). Here's 2 possible workarounds: * Instead of trying to automate the components from what people type…

Hi @Yair, It would be helpful if you could share a screenshot of your workflow and explain what status you would like to move your issue into. The issue can be related to missing transitions, workflow conditions, statuses that are not correctly mapped to board columns, ... 

Hi @Luna Sokol, If you use Tempo and you seem to want to follow up your team's timesheets on a daily basis, why not set up a team report for the current week or month, where you can track your team's worklogs at any time without email notifications? Just add a daily reminder in your agenda to check the report and you…

No, it doesn't. I overlooked the fact that you are trying to update your components while creating an issue. Why don't you add all components in 1 step instead of editing your issue twice? You should be able to add more than one component in a single action. Like this:

Hi @Mosab Albutery and welcome to the Community! This is a performance thing. If your done issues stay on the board, your screen after a while starts loading slower. And since done issues do not need any more work, they are hidden after a while indeed (in general 14 days). In company managed projects, you can update this…