Mass.gov Feature Request board

Suggest new features, see what others have suggested, contribute use cases, and vote for your priorities. This board is open to the public.

Feature Requests

If you have an idea for a feature that would make your work as an author or editor in the Mass.gov Content Management System (CMS) easier, better, or more efficient, you can use the Feature Request board to make your suggestion for the Mass Digital development team.

You can contribute to the CMS’s development (even if you don’t have any features to request) by interacting with all the suggestions others have made on the Feature Request board. You can comment on, vote for, and track the suggestions that matter to you. Your comments, and the details that you provide to support them, help Mass Digital’s development team identify the most consequential ways to improve Mass.gov.

Feature Request board is on GitHub

To use the board, you’ll need a GitHub account. If you don’t have one you can create a GitHub account for free. ‌You can bookmark the board, or access it in the “projects” tab from the Mass Digital GitHub repository’s navigation menu.

We highly recommend you create a username using your state email address and full name. This will make it easier for us to reach out to you directly. Also, this will direct email notifications about requests to which you’re subscribed to your work email.

The Feature Request board is open to the public. Your use of the board should adhere to the professional standards we expect of one another, and which the public expects of state employees.

What happens to Feature Requests

Each request is represented by a “card.” As the Mass Digital development team makes progress on a request internally, we’ll move that request’s card across the board’s five columns.

The New column is for suggestions so recent that Mass Digital hasn’t had a chance to discuss them yet.

Once we’ve begun talking about them internally, we’ll move them to the Under Consideration column.

If we think we will get to something in future, we’ll add it to the On roadmap column. This doesn’t mean it will definitely happen, but we hope to dedicate the resources to do it in a future quarter.

Once we identify resources to implement a feature, we’ll move a request to the Queued for work column.

Finally, when we’ve finished work -- or if we determine we can’t work on the request in the foreseeable future -- we’ll move it to the Done/No Further Action column.

‌Want to dive in right away? Here’s how in 4 easy steps:

  1. Head over to the Feature Request board

  2. Click on a request to review, vote for, or comment on...

Last updated