Comments
-
I agree with @Dirk Ronsmans Start with looking at a sample ticket that you are noticing this happening on, and look at the ticket history. From there, you can see if it's someone doing it manually or if it's an automation. The workflow could have also changed and is automatically unassigning it from the developer as well.
-
Hello and welcome to the community. If you're migrating from one instance to another and you don't want to reuse the project code or can't. I would recommend exporting all issues and fields from your project via the advanced issue search tool as a CSV file. That way in the CSV you can remove the columns you don't need then…
-
Love this. I hope I can catch one!
-
It might be worth doing a retro to see if you can find out what's changed recently. You can do a broad retro to find out if it's an overall team thing, and then you can do specific project / milestone / sprint retros to find out if there's something specifically related to a chunk of work that is causing the problem.
-
This is definitely something I'll be bookmarking for the next time I'm in France. This is awesome. Thank you!
-
That's pretty cool @Dave LIAO I haven't had a nickname like that yet. If I did though I don't think anyone would really tell me. lol
-
Looks awesome. I wish I could join today.
-
Hi and welcome to the community. Atlassian Access is used to sync between Azure AD and Atlassian products. It is available on the Standard, Premium and Enterprise plans for your products. Atlassian Access is a separate product that will need its own licensing. It is needed however if you want to sync your AD to their…
-
It should if you just create new SLA filters and add that created part of the JQL to the end of the filters. Be sure to also add the opposite of the following to your existing SLA filters so your new tickets don't use the old SLAs and created <= yyyy-mm-dd
-
Another thing you can do is add something like: [TEST] to the front of your Summary field in those test tickets to show they are testing and not part of actual work.
-
HI @AbrahamA To my understanding it can't be configured to only work on a go forward basis. It will always redo the SLAs for all tickets. To bypass this, you can as part of your SLA filters configuration add the JQL and created >= yyyy-mm-dd I hope this helps.
-
Hi @Marcela Králíčková Welcome to the community. Have you checked your company's spam filtering and mail settings? It is possible that if your company is using something like mimecast then it can be filtering out the emails from reaching your inboxes. I hope this helps.
-
Hi, You will need to see if Manual Sorting is turned on for that structure board. It looks like they are trying to sort it themselves but it's locked in somehow based on either the structure board configuration or the view configuration that they have. I hope this helps.
-
Hi @Lauri Pantos I would suggest creating a JQL that would check for duedate <= 0d and assignee = currentUser() to pull in anything past due. You can update the date to be what you're looking for so.... -7d is a week past due for example. Then save that filter and subscription to everyone that needs to get the emails. If…
-
Hi, A question for you. Is your email address for someone that has an account in your Jira instance? Or are these emails that aren't in your setup? Just asking because it will help guide the possible answers from the community.
-
Hi @David Meadow Based on what you're describing I would personally do the AD migration work done first, then do your Jira migration. The reason I say that is because then you can validate that your AD migration was done successfully with your server environment being intact still. Also, from experience AD migrations are a…
-
Hello! Let's get this show on the road, eh? * When did you first time find out about Jira?* Back in the fall of 2015 * Where are you in the process of adopting Jira? Only considering it or already implemented and looking for some extension?* An avid user of the product in all sorts of environments. Some cloud, some DC,…
-
That is correct. It only supports one across the site.
-
Hi all! My name is Heather and I'm one of the Community Leaders in Canada. I've played a variety of roles in the Atlassian ecosystem ranging from customer to partner and everything in between. I'm also a PMP and Certified Scrum Master within the IT industry, and most of the companies I've done heavy agile with are in the…
-
Hi @Renee Tibedeau Welcome to the Community. I'm not entirely sure if the complexity here is something that automation can handle itself within a single automation statement. However, you can try looking at Scriptrunner. There are scripting capabilities there that could do this easily enough for you. If you want to…
-
@Eva8 @You said this is for JIRA version 4? Are you using Service Management by chance?
-
Hello Good luck on the interview! I think an important thing to remember is how you’ve used these tools in the past. How you solved problems not just related to these tools but in industry. It’s important to understand that the product is constantly changing and knowing how to problem solve and perform research is key.…
-
I agree. It appears the : is missing from the url.
-
I have to agree with @Nic Brough -Adaptavist- as a user of the product, it makes it hard to figure out what's being considered or what's been even seen at times. I've raised up my feature requests in person when I attend Teams and Summit in the past because I thought they were important enough for the community. I know…
-
Hello all! I've been using JSM for about 2-3 years now. Originally on Server and now in the cloud. It's been fun learning how to use JSM beyond the original use case of a service desk or team.
-
These look like they'll be fun to try to earn.
-
That also helps a lot. Thank you.
-
I'm looking forward to doing this, this year!
-
This page will have the markdown you need for the comment. Give it a go. https://support.atlassian.com/jira-software-cloud/docs/markdown-and-keyboard-shortcuts/