Comments
-
This change makes it HARDER TO FIND. Instead of being on the right side where I can ALWAYS SEE IT you moved it to the header and ALSO MADE THE HEADER NOT STICKY. So now when I'm in the comments, I cannot see the status OR THE TICKET THAT I'M WORKING ON. I work on hundreds of tickets a day. I'm in and out of a dozen or more…
-
Yes, I agree!
-
But even the board that I created with a filter that includes multiple projects, the ONLY options across the top respecting the filter is the Kanban one. Every other option is showing me everything in the Product Management Project which is useless. I need to see subsets of work which is why I create Boards in the first…
-
Yes, if the board already exists, you can see it there. I'm talking about adding NEW boards that aren't just for the one project, which is what the Create Board plus sign does.
-
Yes, I agree, that left nav collapsing list is annoying and takes LONGER to get to things. And I'm on team 100% every search field should allow me to use jql AND free text search.
-
And when I use the Search bar at the top, if I use JQL there, it gives me useless search results and then turns my JQL into a textfields search.
-
What is going to happen during the weeklong period of potential downtime? What happens when an automation fails? We use this to track when customers get releases and it's tied to our User Creation process. Will it auto-resend any failures that occur?
-
It worked for me once I bought the Premium version of Power Automate and followed the instructions provided byAtlassian and created a brand new Workflow in Power Automate. My Teams channels are displaying the popup messages and contain the content of the Jira ticket that I have set up.
-
THANK YOU!! This is exactly what I needed! Works great and I'm glad that the little yellow line stays there as a visual reminder that I have comments hidden :)
-
I worked directly with Microsoft including a two tier escalation and much back and forth and there is NO WAY AROUND BUYING A PREMIUM LICENSE FOR TEAMS. It's SUPER angering that it used to work for free and we're now being forced to pay for it. The user creating the automation script MUST have a Premium License for Teams…
-
There is a problem with this method though. Once I'm in an organization, if I make a comment on a ticket that is Waiting for Customer, it thinks I'm replying AS the customer and flips it to Waiting for Support. This is not desirable as we're on calls working with our customers on tickets. So each of our reps has to only…
-
Yes, they can show one ticket at a time, but they're working through the customer's list of open tickets when they're on the phone. I figured it out with help from our Jira admin: 1. In the Support project, go to Organizations 2. Added myself the Organization. 3. Now, when I go to the Portal and click on Requests, I can…
-
I found out how to do this. In our Support project, under Organizations, I added myself to the Organization that the customer is in. This then allows me to filter requests by Organization from the Customer Portal.
-
That wasn't helpful.
-
but in order to do that, we need to create one user per organization per Support person. Support Manager A has customers A, B, and C. They need to meet with each customer separately each week to review their tickets. In order to use the Customer View in our Service Desk Portal, we would have to get three email accounts for…