Jack Brickey Expert

yep this is weird. I plan to check w/ some of my recent user adds and see if I can reproduce. IMO this is something that Atlassian Support should chime in on so @Deborah Genevro you may wish to open a ticket.

easy enough just takes a bit of setup. To get you started here are some basic steps. I think if you play with it you will figure it out. * you will need two SLAs, e.g. Group1SLA and Group2SLA * you will need some field to trigger between Group1 and Group2. You could create a custom field or my preference generally is to…

Unless I'm mistaken, and I know I'm not for my instance, election of the new UI is by user not global. Now it may not be the case for new accounts?

how about we start by simplifying the SLA and see if we can get it to stop or create a new one as a test. leave everything else off and simply have Start when Vorgang erstellt Stop on kommentar: Fur Kunden

unfortunately I am not able to assist. maybe others can provide some direction. Now to be clear you need to be on Server not Cloud to change code but expect that is obvious. :-)

no this isn't possible w/o changing the code.

in the portal in the top right you should see "Requests" w/ a number beside it.

@Nicola BurgessDelete when sprint ends and before next begins. 

While it isn't free you can certainly sign up for a 10 user instance ($10/mo). Sure they should offer free if you are using for sandbox. However, my experience is that the things you can admin are pretty limited compared to server and changes can be pretty forgiving w/ basic care practiced. I have yet to break anything…

Click on magnifying glass and enter the ID. There are a number of threads that discuss this as well as other "newness" topics.

might be time to contact Atlassian Support

if it is happening on multiple browsers then cache clearing unlikely to produce different results. Are all users seeing this? 

weird. is it persistent after clearing cache? different browser?

indeed! great article. Once you have everything figured out you should either accept this answer OR maybe better construct a new succinct answer and accept it as this will help other in the future.

Precisely! I was just looking at your charts a bit ago and was thinking that might be a contributing factor. Good find!

do you mean "Customer request type". Try that.

@Andrea Caponio, I agree on the surface that the prediction shouldn't be 4x. I wish I could offer more advice but w/o seeing the details I can't say for sure. I haven't used the Version report for a couple years now and recall when I first started it was confusing for me but ultimately was able to decipher the deltas…

Without seeing the details e.g. screenshot, I can only suggest the reason is that the current velocity of getting work done. There is the theoretical value and the predicted value. Theoretical = sum of estimates and predicted considers velocity. 

I assume it was working and stopped? If this persists I would contact Atlassian support.

hey it's a slow thread! ;-)

agree. magnifying glass is your friend in the new UI. Not perfect but it generally gets me to where I need to be.

@ServiceDesk, routing is a generic term but expect you mean assign. I will see if I can offer a solution. In JSD agents typically work issue via Queues. I would suggest that your two groups (Lab manager, engineers) would equate to separate queues. based upon what you stated I would define the queues as follows: Engineers:…

re: allowing editing of closed issues added as separate answer as it is separate question: https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html?_ga=2.52986091.272351579.1516632992-174962726.1509369656

indeed the likely candidate. you would need to reopen, edit, close.

unsure the exact cause but will offer the following approach to figure it out. assuming there are multiple statues w/in the list try breaking them apart. change query to be by specific status. See where the bulk edit fails.

no worries! that is why we are all here...to help. please accept answer via checkmark if you find this works for you.

u r welcome...please accept answer if it works for you by clicking the checkmark. this helps others in their search.

@Matthew Downs, you need to simply have different Issue Types so you can associate the approval workflow only to Purchases. I would create an Issue Type called "IT Help" and dedicate this to email and you may want to hide it from the portal as well. This issue type will have a basic/default workflow. Then create the…

the user needs to be assigned to the role of Service Desk Customer. If the 'customer' has a Jira account where JSD is hosted they can only view the JSD project if you give them (or group they are in) Browse permissions.

@Gerd_Huhn, you can add a post function to the transition between the statuses. Use Update Issue Field and set Assignee to unassigned.