Dan Breyen Community Champion

1 - Start on time. Be respectful of the people who showed up on time. 2 - Stick to the topic. If meeting meanders off, bring it back to the topic. 3 - End on time or schedule more time. If you need to go over time, check with your attendees if it's OK to go over. Also be respectful of the people who might have the space…

Would be a great enhancement to manipulate them or at least hide them so you can remove ones you are not using any longer.

I just started digging in. I do lots of searches for "Atlassian JSM xxxxx" on how to do stuff. There's the support, Community, and jira sites for looking up KB articles, community help and existing bugs. Good luck!

My automation is processed on the Linked issue of the JIRA ticket, which is the JSM. So all of my {{issue.xxx}} information is from the JSM ticket. Do you know if I can link information from the JIRA ticket?

You have to talk about slinkys if you're talking about stairs!

That would still work, you can look up the linked issue type. I'm doing something similar:

There are two Automations in the library to deal with something very similar to this. One is to mark all sub tasks Resolved when the main task is Resolved, and the other is to mark the main task Resolved when the SubTasks are Resolved. You could probably tweak those to meet your needs. I'm not a Automation expert, but it's…

All good things come to an end. Tragically, the timing of the crash and 9/11 didn't help Concorde. Will be interesting to see if the Next Gen Supersonic becomes a reality.

I refer back to Steven Covey. First Things First. That book helped me to prioritize projects based on size & urgency.

I haven't played with it very long, but I think you could use the diff function for dates and then use the businessDays units. I think you're looking for haven't been updated in the last 3 BUSINESS days, so this might work. Check out this page. Jira smart values - date and time | Cloud automation Cloud | Atlassian Support…

I think you could do this... But the automation would need some sort of trigger. Would you be checking if it was saved today? Otherwise you could create some sort of rule to run every day and go through all the issues, but you still would need something for today's date to be compared with.

If I recall correctly, there is a similar automation in the library to do this with sub tasks. If the main task is complete, close the sub tasks, and if all the subtasks are closed, close the main task. you might be able to use those delivered automations as templates.

I'm not answering your question per se, but I was able to create an automation rule in JIRA that notifies the assignee of the linked JSM Service Request. So the Assignee gets notified that the bug was fixed. Maybe that helps for future use. You might be able to use the "issueLink" JQL field to get your query. Advanced…

Thanks, but I'm hoping this would be built into the application instead of requiring a paid add on.

Buy in is important. Giving some points as to why this needs to change, and how it will help addresses some concerns about "Here we go again, just changing for changing sake". When people know why something is changing, it can ease some fears of the change.

Softskills are important for communication. If your Top Performers can't communicate with the rest of the team because of their softskills, It can become a bigger problem.

Buy in is important. Giving some points as to why this needs to change, and how it will help addresses some concerns about "Here we go again, just changing for changing sake". When people know why something is changing, it can ease some fears of the change.

Change is hard. Without buy in, change can also be unpredictable and unproductive.

Meeting for meeting sake is a bad practice and wasting time.

Don't always assume that the same people have to do the same tasks when you start a new project. I agree, some people are good at specific tasks, but you also need to cross-train so other people can grow the team's knowledge too.

Gotta celebrate the victory of finishing the project. It helps put a conclusion to one project before starting another.

“By failing to prepare, you are preparing to fail.” ― Benjamin Franklin

Can't stop learning. Even if the company doesn't provide classes, you need to find them on your own. I'm always finding books or podcasts that can help with personal growth. For teams, schedule a Team meeting to review a feature or part of your project to show the rest of the team. It can drive innovation.

Any chance to break up the monotony of the meeting can be very productive.

HERE HERE! Meeting for meeting sake isn't productive. If the status hasn't really changed this week, skip the status meeting. Focus on changing the status for the better next week.

Having worked at a few different companies, it's interesting to see how different companies close out the year. End of year seems less an event after covid.