Filer - Update filing processors to work with alternate name changes for non-firm filings about entity HOT 5 CLOSED

Don't think it will degrade the velocity. I've since moved way from the idea of a ticket per filing...think some filings are a bit too small and it could be that there won't be much to update.

As for tickets to sub in, I think #20165 and #20166 should be already to assigned to your team and ready to go.

from entity.

Olga says it's OK to remove this from our sprint and bring in the other 2.

from entity.

@OlgaPotiagalova @ketaki-deodhar @severinbeauvais After observing the past 2 sprints, I think some of the tickets I have created are a bit heavy. I was thinking of breaking this ticket down to a ticket per filing + the filings respective unit tests multiple tickets. Some of the more complex filings will be separate tickets and some of the simpler ones will be grouped together in a few tickets. Also respective unit tests will be addressed in these new tickets too.

Are you ok with pulling this out of your sprint for now? I believe you still have some legal name tickets you can pull in if we pull this one out.

from entity.

Ok by me as long as it doesn't degrade your velocity. Do you already have other tickets to sub in?

from entity.

Closing this as other tickets have now been cut.

from entity.