Walter Buggenhout Community Champion

Hi @Michael Q. Terry, The assets field is part of the old Insight marketplace app that is no longer available. As of March 31st, Insight has been relaunched as a new product, integrated for free in the premium and enterprise plans of Jira Service Management. It comes with a totally new Insight custom field that offers…

Hey Ben, Sure. Those products target different teams with different needs. All products are built on the common Jira platform. They share some very important concepts like: * issues are always stored in a project; * issues always have an issue type; * they are always moved from to do to in progress through a workflow * the…

Thx @John Funk :-) Maybe the story did not entirely go as I described it, but an adventure it sure was! And my 9-year old really was the star of the day at the airfield! 

I don't know if anything has changed in the meantime, but the video is triggering now for me (on one occasion at least)! #lockdownparty

Hi Daniel, Welcome to the community! I hope you can indeed make the jump to 10.000 users over time. That would mean both your organisation as well as your Jira implementation have become an amazing success! Just to put things into perspective, though: be aware that those 7$ are the average price per user, not for the…

Hi @Ben Werner, As far as I know, you can't update that. So I'm afraid this will be some related philosophical advice ;-) ... Jira has 3 main types of projects (and even underlying products): Jira Software / Jira Service Management / Jira Work Management (fka Jira Core). This subtitle indicates what type of product this…

Hi @csawai1, I always recommend people to look at boards as the home for work of a single team. Ideally, a team has one single board where all its current work can be scheduled and moved from to do towards done, visually. Whether that should be a scrum or a kanban board is very much depending on the type of work (is your…

My first summit was back in 2015, which was opened by Mike and Scott disguised as Daft Punk. I only missed one since. That very first still is the one I remember most of, as it was a really overwhelming experience. Next times that changes a bit, as you have a better idea of what to expect. But by now I have met so many…

While on a roadtrip in Holland, we spent a couple of days on the Island of Texel. You only get there by boat, it's really quiet and it has some great and very extended beaches, good roads for riding the occasional bike and so on. While we were there, we noticed we could take a small plane for a flight over the islands.…

You will keep running into the same problem that you cannot reference a board, Bonnie :-). The Easy Agile Story Maps live inside your board and do use the data delivered by your board filter to add their story mapping features to those data. But as your board filter is based on the value you entered in the Scrum…

That, I do know :-) You can find it from products > Jira. Then, one of the sub categories is New to Jira. You can find it from the navigation on the right hand side there. Or even easier: just click this link :-) 

I see what you are trying to achieve, @Lopes, Bonnie Q. The problem is that an issue is not created in a board. It is created in a project. If you look at your create issue screen, you will always have to select 2 fields before you can continue: * the project where your issue will be stored; * the issue type you want to…

Oh - one more thing: I also noticed that challenges with multiple steps (like this one) don't appear in the in progress filter unless at least one of the parts is fully completed. I think it would be useful if this happened as soon as there is some progress - but I don't know if that is possible.

Hi @Novakopa, Yes there is. In your JSM project, navigate to project settings > customer notifications. This specific notification looks like the customer-visible status changed notification. When you click edit there, you will see a screen like this: Under content you can modify the message that is being generated. Don't…

Hi @[deleted], As long as you set up a separate service desk (project) for each customer, you should be perfectly capable to enforce restricted access to each of those. You have to make sure to only allow access to your service desk for users added there by agents/admins: The setting can be found in each project…

Hi @Prabhu Prabhakar, A post function is designed to perform an action, essentially update something. JQL is designed to search for issues, not updating anything. So I assume you would like JQL to act as a condition you would like to use prior to an update on one or more issues. In most cases, automation rules are a great…

Hi @Charles Delaporte, There are many ways you could set this up, but just looking at the way you describe your goal and from the table you added, you might start by creating an Epic for each report (Report 1, Report 2, Report 3). Then for each improvement create an issue in that Epic - make sure to set up a custom field…

haha, great consensus here :-)

Hi @Anumalla Nithinraj, Clone is the built-in default option in Jira to copy an issue. This is a good thing, but it has limited functionality. Deep clone is a similar functionality offered by a marketplace app called deep clone for Jira, which extends that functionality. Apparently you have that installed on your Jira…

Hi @Lopes, Bonnie Q, If I understand you correctly, you have different boards for each team that shows the issues for those teams specifically. If so, you'll need to understand / define what makes an issue belong to each team. Maybe that is because each team works on different issue types. Maybe because it has specific…

Hi @Miyoung Mary Kim, I am not sure what you mean when you say "they are added in the setting". Nevertheless, there's 2 places you could/should look in order to grant the proper permissions to your plan: In the settings of your plan itself (inside your plan, from the cog icon next to the plan's name select Configure and…

Interesting, @Zachary Brown. Welcome to the Community! There may be a story in that to share one day ;-) 

Great to have you on board, @Şeyma Yıldız! Have an awesome internship! 

Welcome to the Community, @cesar.alves! 

I am not sure what you mean with you added them as default users. That does not sound right, to be honest. It does absolutely matter though what you say about the team-managed template. Permissions in team managed projects are managed differently there and are quite new. All the details of those permissions are described…

Hi @Joan Andreu Juan Torrens, I don't know why this is happening, but you have too many %%%%%%%%%%%%%% signs there in your screen (definitely in the instructions too, so don't blame yourself). Normally, this should work: %%CURRENT_DATETIME%% 

Hi @Christopher Alexander, Adding people to the Service Desk Team role does not make people agents. That is only the case for users who also have product access to Jira Service Management - and that is a different thing. If the people you refer to should really only have view rights on the tickets in your service desk…

Hi @Christopher Alexander, As long as those external users have access to Jira Software or Jira Core, they should be able to access issues on the dashboard. You should however add them to the Service Desk Team role instead of the viewer role. Additionally - if you have built saved filters to populate the gadgets on your…

Hi @Hema, You probably refer to the solution described in e.g. this related question, where issues.stories.length is uses to check for open issues in the epic. It also mentions that issues.stories refers to all issues at the level below an Epic: // The stories paramater returns all the issues below the Epic issue to allow…

Hi @Matthew Lane, Setting up a company managed project as a template for your division is an approach I would strongly recommend for the use case you describe. Projects you create from that template (when you create a new project, check the option to share the settings of your new project with that template), will then…