Hero cards allow you to bundle up related cards. They are an abstraction layer living between decks and card checklists. If you use agile terminology, you might think of them as epics. In Codecks there is more to them. In combination with journeys they allow you to construct awesome repeatable asset pipelines.
Before using hero cards you should make sure that they are enabled in your organization settings.
Creating hero cards
Hero cards contain one or more sub cards. There are various ways of creating or editing hero cards:
Drag and drop a card onto an opened card to add a sub card to the opened card (which will become a hero card unless it already is).
Attach an existing card using the hero sidebar (click the hero button to the right side of opened cards).
From the hero sidebar you can also create a new card inline and attach it as sub card immediately.
Use the hero sidebar to select the new hero card of a card.
Select one or more cards and use the bulk action bar to set the hero card or to create a new hero card.
Each sub card can only be part of one hero card. Hero cards may not be part of other hero cards.
Working with Hero Cards
Hero cards are recognizable by the golden color. Their own workflow states are disabled, their effort is calculated by adding up the efforts of contained sub cards. They can have a priority or be assigned to a milestone.
To get a quick overview for the contained sub cards hover over the progress bar of the hero card. The progress bar will fill up as more cards are set to done. Cards that are in progress, in review or blocked are shown by the respective colors as well.
You can see the full list of contained sub cards and jump between them by opening the hero sidebar. To open the sidebar you can click on the header bar of hero cards or click on the hero icon next to opened cards.
The sub list shows all contained cards including their title, owner, priority, effort and milestone. You may remove any sub card from a hero card again by clicking the small X on the sub card entry. Use drag and drop to change their order.
To see the sub cards in full, you can click the magnifying glass on top of the list to get a view of all sub cards in their regular card size. You can also use the action bulk bar from here, for example to assign an owner to multiple sub cards in one step.
Sub cards are fully functioning Codecks cards that have access to all the workflow and conversation features as before. This for example allows to separate the sub tasks of a bigger feature into different milestones and to different owners.
Filtering sub cards
Whenever you’re viewing a deck or milestone that contains hero cards and sub cards, you can find an additional hero filter button on the header bar. The filter enables showing/hiding sub cards that are contained in hero cards currently part of the same view.
Journeys are an awesome way for working with hero cards. They allow you to template full sequences of sub cards and to activate them with one mouse click.
Journeys are always associated with decks. To prepare a journey, open a deck and click on the journey button on the deck header bar. This will open the journey setup page where you can edit the start card. You’re also able to add and edit step cards.
When a card is created within this deck, the start card’s content and properties will be applied. Use it for a card text with bug reporting guidelines or a checklist for new team members onboarding or to apply a default tag or default owner for all cards in a certain deck.
Whenever somebody clicks on the journey icon on a card within this deck, the card becomes a hero card containing a list of sub cards that mirrors the step cards that have been setup for this deck.
All these features combined work towards allowing for a unique asset pipeline system.
Once you’ve triggered a journey all the cards are created. There are no restrictions in regards to what you can do with the cards afterwards. Edit, add or remove sub cards as it makes sense to this particular hero card. Changes to journey setups don’t affect hero cards that were already created using that journey.