Group programming

Tags: Flow

Enabling the group programming feature in your account allows you to visualize contributions authored by multiple people. Use group programming settings to customize how group work is credited across each individual.

Choose how Flow allocates credit for Coding days, Commits per day, Impact, and HALOC metrics, including Rework, Efficiency, New work, Legacy refactor, and tt100.

Who can use this?

 Core
Plus
 
  


Enabling Group programming

In order to turn on group programming you will need the Configurations permission.

To find Group programming:

  1. Navigate to the Settings menu.
  2. Click Configurations located under Report settings.
  3. Click the Group programming tab on the Configurations page.

Note: Flow only applies Group programming setting changes to new incoming data. It won’t reprocess old data automatically. For this reason, it’s recommended that you enable Group programming before importing your repos.

If you import a repo before enabling Group programming, the previously imported data won’t have the new settings applied.

To enable group programming:

  1. Navigate to the Group programming tab.
  2. Toggle the Enable toggle On.

Enter the label you want Flow to apply to co-authored commits from into the text box under labeling.

back to top


Assigning work to others

Use the toggles in the Assigning work to others tab to set how Flow identifies when a commit is co-authored.

To toggle on Using Co-Authored-by in the commit message so GitHub can mark commits with multiple authors:

  • This convention is used by GitHub to mark commits with more than one author.
  • For group commits authored solely on the commit message, you must include Co-authored-by with an email address or a GitLab username with an email address.
  • There are tools on the market that you can use to help you add this into your GitHub. You can find the tool teams on this GitHub page (external site, opens in new tab). Pivotal offers another alternative.

To toggle on Using multiple names in the user.name and user.email fields so you can manually mark commits with multiple authors:

  • This toggle is useful for commits with user.name and user.email fields similar to:
    • Jen Smith & Robert Aspens jsmith@mycompany.com, raspens@mycompany.com
    • Jen Smith & Robert Aspens raspens@mycompany.com

When the Using multiple names in the user.name and user.email fields is toggled On, the Prefixes, E-mail delimiters, and Name delimiters text boxes are active and editable.

Enter any prefixes or delimiters you want Flow to check for. Flow labels any ticket containing these values in user.name or user.email as group work.

Click the Add another button to enter additional values. Click the X button to remove a value.

For example, a commit’s user.name field contains Jen Smith & Robert Aspens. The commits user.email field contains jsmith@mycompany.com,raspens@mycompany.com.

In this example, Flow labels the commit as group work when a text box under Email delimiters contains , or a text box under Name delimiters contains &.

To mark individual group commits, see Manually marking a commit as a group commit.

Allocating credit for group work

Configure how Flow assigns credit for group work. Split the work between contributors or give each contributor full credit.

Choose how Flow allocates credit for these metrics:

  • Coding days
  • Commits per day
  • Impact
  • HALOC metrics, including Rework, Efficiency, New work, Legacy refactor, and tt100.

Click Save Changes once you’re done adjusting your group programming settings.

back to top


Viewing group programmed commits in reports

Once you’ve enabled group programming, Flow shows co-authored commits as squares in Work log.

To view group commits in Work log:

  1. Click Reports to navigate to Flow’s Reports home page.
  2. Click Work log in the left navigation under Daily check.
  3. Check the Group box in the custom filter on the left.

Click a group commit to see more details.

If Flow missed a commit or added too many authors, update the commits manually.

Learn more about manually marking a group commit.

back to top


If you need help, please email Support (opens email form) for 24/7 assistance.