Walter Buggenhout Community Champion

Hi @Marc-André Lanciault, There can be a conflict when your internal users also have an agent license to JSM. As explained in this support article, your internal notification scheme takes precedence over the normal customer notifications for users with a double role. So, first of all it is definitely worth having a look if…

Hi @Aitor Bernis and welcome to the Community! No. The Community is a great place to connect, learn and ask all kinds of questions, but for technical issues and bugs, you should raise a ticket through https://support.atlassian.com/contact/#/ Hope this helps!

Hi @Kipngetich Cornelius, You have - most likely - created a Jira project (not Jira Service Management) for your longer projects and these don't have a portal, nor visibility for your customers. It is quite common for organizations to have a service desk portal available to capture requests from customers and - at the same…

Hi @Andrew Makmur and welcome to the Community! You have a timeline associated with your board. If you click in the roadmap section next to an issue there (try an epic first to be sure - in your project's board settings, there is a switch to enable/disable scheduling on task level issues. If that is not enabled, then you…

Hi @pooja shirguppe and welcome to the Community! Is this a backup from a current site or from another site? This is very likely a permissions issue. In your admin console check if there are any users to review access for and check the permission settings on your projects. Hope this helps!

Hi @Mar, Let me assume you have 3 different request types instead of 3 times Request Type 1? A lot depends on how your request types are linked to issue types in your project. A request type - in itself - can't really help you here. But if your request types are connected to 3 different issue types (e.g. an incident, a…

Hi @Pooja N, This is usually not checked with an automation rule, as this kicks in after you have already done something (like in this case: transition an issue to a different status). The common way to deal with this, is using workflow conditions and validators, which allow you to check conditions before you actually…

Hi @AT and welcome to the Community! This looks like a screenshot from a team managed project. Issue security schemes are only configurable in company managed projects. There is an open feature request for adding this capability that you can track here: JSDCLOUD-8749. If you want to implement this today, you'll need to set…

Hi @Lachlan Ford-Browning and welcome to the Community! For questions on automation rules, please do share full details from the automation rule and the audit log. Apart from that - issue links have a different name depending on the direction they are defined at. Implements from the other end can be defined as Is…

Hi @thumuluru.shreya, Rich Filters for Jira Dashboards might be a fit for what you describe. Hope this helps! 

Like most fellow posters, I love the kudos button. As an only downside, I don't think I ever ran out of kudos to give this fast, so can't wait for a refill to be able to feel the happy energy again 😀😀😀 

Hi @kathleen_crowley, When you use JQL to search for time spent, you always risk to be misled. A Jira filter does not return time spent, it returns issues. And so, if you run a search like this: worklogDate >= startOfWeek() ... that will effectively return all issues with hours logged after the beginning of this week. But,…

Hi @Selva Praveen Elango, JQL does not let you compare values of fields to other fields. What you could do in your dashboard is use the text filter I just shared in my previous reply and - on top of that also add the sprint field as a dynamic filter option to your filter controller gadget. If you then apply both, you will…

Ok; if you want to make this work on the dashboard, I would recommend you to enable JQL filtering in your filter controller gadget, where you can enter something like this: "spillover sprint" ~ "\"sprint 9\"" That way, you can search for an exact phrase in a text field. Apart from that, I would really suggest a good look…

Not as far as I know, but the logic is quite simple: you can only use the fields offered by the gadget. If a field isn't there, it is because it is not supported and supported fields for statistics have predefined / structured values.

Is there any reason why you can't add the sprint field as a dynamic filter to your Rich Filters filter controller and filter by the actual sprint itself? That should return all issues in that sprint. I can't wrap my head around why you would duplicate that information into a custom field?

Hi @Vibhor Kumar Agarwal, Most gadgets presenting statistics in some form (a chart, a heatmap, ...) only support custom fields that have predefined data, such as: * user custom fields * labels * components * select lists Text fields and (some) custom fields that belong to marketplace apps tend to be unsupported as it does…

Hi @Selva Praveen Elango, I don't quite understand why you are making such a complex workaround. Can you explain what you are trying to achieve and why you don't simply run: Sprint in openSprints() That dynamically returns all issues in the current sprint, from the actual sprint itself. You should be able to search on any…

Hi @Abdelkader Wahb and welcome to the Community! Customers of your service portal will only have access to their own tickets or tickets shared with them. That is not something you can change; The approach you currently apply by adding valuable solutions to the knowledge base, is the very best thing you can do. It…

Hi @Ba11zooka and welcome to the Community! To answer this request, it is essential to take the triggering event into account that stops your SLA timer. Since you refer to Time to resolution, the common trigger for this is resolution set. This event also sets a system date in the resolved custom field, that you can then…

Hi @Jeffrey_Denton, When you add a gadget to a dashboard, it does not automagically inherit the fields you included on your filter in the issue navigator. You need to add those fields to the dashboard gadget as well, but this should be possible: Hope this helps!

Hi @Bryan.Singh and welcome to the Community! I see from your screenshot that you are in a team managed project. This type of projects does not allow you to create multiple sub-task issue types. There is a feature request for this that you can track here: JSWCLOUD-20901 (though the most recent update does not suggest it…

Hi @Taran and welcome to the Community! As far as I can see, there are no issues showing up on your timeline at all. I suppose you have created issues, but no epics in your project? It is true that issues do only show up on the timeline when they are linked to a parent epic. So after defining one/more (parent) epics,…

Hi @Nancy DeMattos, No; idea is the only available issue type in Jira Product Discovery. The team behind the product adds tags to ideas to differentiate between different types of ideas. Hope this helps! 

Oh, ok. That is quite limited, to be honest. It really isn't much more than this: In short, it is a list of tickets with - again - a limited set of available fields and just a couple of filter options. It definitely meets easy and clean, and as a consequence does not offer a lot of detail. The intel is on your end of the…

Hi @Chris Green and welcome to the Community! Not as far as I am aware of. But I have the impression that there is another question hidden underneath the surface of this one. What problem are you trying to solve? JSM runs on computers and they are quite binary in their ways of processing stuff. So, if the list of tickets…

Hi @Kristen Butler, As per this community article, this should be possible. Hope this helps!

Hi @Kateřina Blahová, instead of transition the issue to ... your action should be edit issue. You can then select the labels field and copy the value from the parent issue there. Hope this helps! 

Hi @Anne van Susteren-Finger and welcome to the Community! That is a very valid point. If there's too many sprints in the backlog, it becomes quite difficult to see the actual work. Jira does not let you filter away sprints. As a best practice, talk to your teams and advise them not to do this. Sprints are designed to plan…

Hi @David Laine, A Plan is a sort of sandbox. It pulls in data from Jira sources, which can be a board, a project or a saved filter. Once issues are in a plan, users can update fields, set start and end dates etc. Since a Plan is fundamentally a planning interface to plan across multiple projects or teams, changes are only…