Jack Brickey Expert

wildcards aren't supported OOTB. While I haven't used myself I have seen others reference JQL Tricks Plugin. Here is a reference that might help.

check for quick filter on, e.g. "recently updated"

speak to your Jira System Admin

So do you mean to say that you want to find all issues that are overdue more that 2 days? If so try this filter status !=done and due <= 48h Notes: * if you have other 'done' statuses then use the "not in()" function and include them all * this will give you the count but if you want to simply watch the count daily then…

I have never seen a case where you can have an epic of epics. Maybe an addon provides this but again never seen this.

You bet. Create a status called say “pause” or "stop progress” or whatever. In the SLA definition there is a pause column, choose the status to pause. You will want to have a transition in your workflow from the pause status back to the in progress status and ensur the SLA resumes when it enters.

Go to Customer Notifications and make sure "Organization added" is Disabled.

espero que el traductor de google lo haya entendido bien :-) 1) haz clic en la lupa 2) haga clic en Ver todos los problemas 3) reemplace el texto en el campo de búsqueda con cualquier JQL que satisfaga sus necesidades de búsqueda 4) haz clic en Guardar como y dale un nombre 5) haga clic en Detalles 6) haga clic en Nueva…

@Steven Harman, you can certainly use JSD for your projects but typically Jira SW or Core works best as you can create projects and have a number of folks licensed to work on tasks associated with the projects. regarding you email notifications the first place to check is the Notifications section to see who receives…

go to Search for Issues, click Advanced and enter into the search field. save the filter and give it a name. share it. there is a lot of helpful info in the documentation. Here is one cloud like to get you going.

If it were me I would leverage an SLA coupled with automation. * Create an issuetype of “loaner” or similar * Create an SLA for loaner of 1 week or whatever * create an automation for breached on loaner to send email

Duplicate

That shoots a hole in the response from Atlassian. While it might be what I see in my instance it isn’t your situation. I will update the ticket with them as such. Ultimately you may need to open a ticket with them so they can log into your instance to investigate. 

sort of. edit the queue and go to the advanced view of filter. Copy it, paste it into the search for issues screen then export

@Brianna Barnes, so I heard back from Atlassian and I have copied their response below. I don't know if this is your situation or not but suspect it is. If so it appears to be WAD (works as designed). To be honest I don't like that answer and I doubt I would implement that way, but I sort of understand it. I haven't tried…

@Jan Visser, Please have a look at your project Automation section. I suspect there is an automation rule that is set to run as 'you'. Whether it is in Automation or somewhere else (addon, system rule, etc) for sure this is the reason. I do hate that Atlassian doesn't have a default system user that can be use for this.…

@Boris Berenberg - Atlas Authority, thanks for chiming in here with this. However, i'm a bit perplexed by this workaround TBH. I thought that removing from an org only placed them back into the Customer list. Maybe the "delete org" action is the trick? Further, in reading back thru Brianna's notes I think she may have…

no answers yet but I wanted to add the results of a test I just performed in the event it helps others more quickly drive this question to closure. Hypothesis: New customers added to a project do not result in that customer showing up under the Settings>People view. * In Project A I have a customer that shows up in the…

so u aren't crazy for sure. i think i'm learning something new about this "people" stuff which BTW is, IMO, a very poor implementation or at least very confusing. I'm not 100% sure what is going on or how to explain it just yet but it appears as if customers don't show up in the people list if their open/closed are both 0.…

let's try two things: * try typing the name of a 'known to be customer' in the search field. if that doesn't produce a result then - weird * try selecting Service Desk Customers in the drop down - if that results in no users then - weirder If 1 & 2 strike out then let me ask a stupid question - are you 100% sure you are…

I'm getting confused now. :-) Can you please share a screen shot from the same location as what I shared?

ok so either they aren't part of the project OR they are in an organization. Let's check the later: * Project * People * look for an organization and select it * look for the users you wish removed and remove them from the org. this places them back at the "customer" level * repeat my previous instructions and see if they…

if you have admin permissions then you should be able to... * Project * Settings * People * choose Service Desk Customers * remove the customer

@Karen Rodriguez, * are you on cloud or server? * i assume the default kanban board already exists that was created when you created the project? * which step on my previous instructions are failing you? 

you simply need to remove them from the projects where they do not belong. If a customer is on multiple projects and you remove them from one project it only removes them from that project. If you want to remove them from all projects then remove them from the User Management screen. Sometimes what happens is that a user…

@Rosa M Fossi, I did not see a response to my suggestion so unclear if it would meet your needs. Your request is to 'remove issues w/ certain statuses from the board'. It isn't clear what you mean by the 'remove' verb but let me restate and add more options here: * Option 1: remove the statuses from the workflow. Sounds…

You can only display the Epic Link not the Epic Key or at least I haven't found a way to display the actual Key. 

Esta es una pregunta frecuente en la comunidad y le recomendaría lo siguiente: https://confluence.atlassian.com/confeval/jira-service-desk-evaluator-resources/jira-service-desk-how-jira-service-desk-works-with-jira-core-software?_ga=2.124184010.1320614320.1525699763-1527993323.1519149877…

Given all the latest info here is my theory and recommendations. Theory: somehow,e.g. workflow change or bulk move, certain issues changed status without going thru the start trigger so they simply never met the criteria to start counting. At this point I’m not sure it is worthwhile beating your head over figuring it out…

See if this helps. You should certainly see the option on your transitions. If you still don’t have any luck let me know and include some screenshots of your workflow with the transition being edited.