Rock does not appear to inactivate "Spam Reporting" email addresses and make the note on them like it does with Bounces. It appears that Rock is getting that information from Sendgrid and so people in a distribution list are failing with Spam Reporting address as the reason.  We are having to manually add notes and inactivate the emails in Rock from the list in Sendgrid. I would like to request that Spam Reporting emails be marked as inactive with a note like the Bounced emails are. Per Michael Allen: That would need to be a code change in the email transport's...

---

Currently the summary grid for Workflow attributes includes Attribute Name, Description, Key, Field Type, & Required ... and the summary grid for Activity attributes includes all of these same columns EXCEPT for Key. While this is not a show-stopper ... it is definitely a pain when you have a workflow that implements LOTS of activity level attributes since you have to go into each attribute to double check this value say for when you're referencing these in a LavaRun action....

---

The Communication Queue block is used by our Comms team to manage what communications need approval. I noticed with some other testing this week that even if there are communications pending approval, they disappear from the Communication Queue block after a few days. Upon some digging in the code, I believe it is because the expiration days is a hardcoded value of 3 here: https://github.com/SparkDevNetwork/Rock/blob/d670d4f1d22229e9b5cc182f9af6846f29f0d0ca/RockWeb/Blocks/Communication/CommunicationQueue.ascx.cs#L200I tested this theory by using SQL to manipulate the CreatedDateTime on a Pending Approval communication to that 3 day mark, and it disappeared from the queue. To find all the communications that are pending approval, you have...

---

There are multiple places in Rock where we collect people's info. There's lots of flexibility as to what is required and what is not. However, one thing missing in our mind is requiring either an email or mobile, not both. It would be great for forms to ask for communication preferences and then email or phone be required based on what they selected. Family Preregister, workflow forms, add to group forms, etc are some places we use often and we have to either require both email and mobile or don't require either. ...

---

I have an array of attribute ids that I am getting back from SQL that belong to a specific category and am looping through all of my workflow attributes and need to check and see if the workflow attribute is in that array (ultimately trying to only loop through the workflow attributes once but pick out which ones belong to a specific category). I'd love to be able to use the Contains filter with a Lava variable. I also tried using a Lava variable with RemoveFromArray and checking to see if the size is less than before, but the Lava variable...

---

Currently, the final option on the "Email Preference Entry" is to mark that you are no longer involved, which is set to inactivate the profile. We generally still leave people as active when they stop attending, but use the "no longer attending" status instead. To that end, it would be nice to be able to change what the no longer involved function did, so we could still allow people to mark that without throwing off their accounts....

---

If we want to encourage staff to utilize the Documentation and RockU videos, and past RX recordings we've purchased, we have to coach them to register an account properly and then we have to go back later and approve them. It's not super obvious to new staff how to do this, and we don't get a notification that there are pending members, so we have to remember to check.It would be helpful to us to be able to invite them and once they accept the invitation, they are automatically approved as a Member....

---

For the new Giving Alerts feature, I could see value in an option to disable Giving Alerts for a specific person in our database. As an example, the "Anonymous" giver we have setup for all anonymous cash that is given each weekend (as recommended in the Finance Manual) is triggering alerts and should not be.I have also noticed this person has their Giving Overview block populated with giving information - I am just beginning to dive into this block and not sure if having this person will skew any metrics/reports we begin to run based off the new giving metrics....

---

The `Workflow Detail` block includes a text label in the 'head' of the block that lists the Workflow Type's name. Set this label to be a link, not just a label, so that it's a breadcrumb taking you back to the Workflow Type....

---

The mobile Calendar View block is great if you have your calendars set up in a very specific way. However, If you have customized you calendars with attributes, there's no way to access these in Rock Mobile with this block.I propose adding the ability to run Lava Commands on this block(currently not supported). With the addition of Lava Commands one could access any attributes on the calendar occurrence, and open this block up for other uses....

---