Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,641,981
Community Members
 
Community Events
196
Community Groups

What determines "inactivity" on a card?

Edited

I'm trying to setup an email report automation for cards that are inactive in a particular list for more than one day.

I've managed to get this to work on a different list, but when I try the list that I want to use, it sends through nothing. Looking at some of the cards in the list, I can see that there has been no comments, card movement, label changes or custom field changes made in over a day (in some cases up to 3 or 4 days), yet for some reason Trello isn't determining these as "inactive for more than 1 day".

Is anyone able to shed some light as to what exactly makes a card 'inactive'?

1 answer

1 accepted

0 votes
Answer accepted
Rafael Dill
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 24, 2022

Hi @Tim Shanaher , thanks for writing to us!

That's really odd. The 'inactive' trigger is the same for every card, if there's no action made on it for the following X days, Y happens. I think the best course for this case would be for you to open a ticket with us, providing the following information:

  • Authorize access to your account, and with that, we can take a better look at the scheduled command.
  • The list that the command worked properly.
  • The list where the command failed to work.

We hope to hear from you again!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events