Set up grants and projects and manage GitHub research work.
Reviewed · 2026-10-12
On this page · 7
1. Create a grant and its projects
- Open Research grants → Create grant. Enter the title and description and save.
- On its homepage choose Create project, enter a title, type and description. This project belongs to that grant.
- If a needed type is missing, ask a platform administrator to add it in Lab management → Project types.
- Assign participants and managers. A project can exist without a source connection; its creator becomes the responsible manager.
2. Read the project overview
- Compare child-project summaries on the grant homepage, then open a project title.
- Review recent reports, events, task status and the material library. Material cards open filtered lists.
- Grant totals include accessible child-project materials. If a total differs from expectations, check filters, classification, permissions and collection time.
- Manage authentication and collection under External source settings; edit research content in GitHub, Notion or Drive.
3. Work with GitHub tasks
- Record the objective, owner, due date and acceptance criteria in a GitHub issue and add it to a Projects board.
- Connect the repository and review discovered boards. For zero boards, verify the actual board URL and organization Projects read permission.
- Review status, owners and dates. Where task editing is available, verify remote write permission and the target board before saving.
- Collect again to verify the remote state. Done or a closed issue does not prove experimental success or PI approval.
Change GitHub Start date and Target date
- Open Research work on a grant or project, then choose Change work. Explicitly select Start date or Target date from the board fields.
- The last collected date appears. Change it as needed. Saving an empty date clears that date on GitHub.
- Confirm the remote change and select Save to GitHub. A matching date in the GitHub response produces a confirmation. The local list refreshes after collection. If only acceptance is confirmed, check Recent work change requests.
- Concurrent changes to the same field or board configuration are not overwritten. Check GitHub and collect the latest values before trying again. Unrelated comments or other field changes do not block the date edit.
- New work at grant level offers grant-wide and child-project boards you can manage. Enter Start date and Target date separately. Check for an already-created issue after partial failure; the platform does not automatically create duplicates.
4. Create an issue from project research work
- Open Grants → grant → project → Research work and choose New work/Create issue. You need project management permission and a write-capable GitHub connection.
- Select the actual destination board and verify its repository.
- Enter a title, objective and acceptance criteria; select multiple researchers and check their GitHub IDs. Each must be assignable to issues in that repository.
- Choose Status, Priority, start/due dates and supported board fields. Start date defaults to today. Size is the board's work-size value, not headcount or automatically calculated hours. If Priority only offers Unspecified, check the board options/mapping and collect again.
- Review related scopes, researchers and tags. Confirm the remote write and save, then inspect the actual issue, board membership, assignees and fields on GitHub.
- For partial or uncertain results, check GitHub first. Do not create another issue without checking whether the first was created.
5. Shared sources, wiki links and scoped popularity
- If child projects share GitHub, Drive, Notion or Zotero sources, connect them once at grant level. Connect project-specific sources to that project.
- Keep important sites and reference links with explanations in the grant wiki, including project-specific links. Adding a wiki link is separate from connecting external sources or collecting document content.
- Grant popularity is scoped to that grant; project popularity is scoped to that project. It is different from lab-wide popularity.
- Detailed progress/work/material summaries may load when expanded. Check search filters, membership and deletion state for missing entries.
Report scope on grant and project pages
- The progress summary and recent reports on grant/project pages refer to reports linked to that scope. Similar titles or the same author do not make another scope's report a report for this project.
- Open report details and check the target scope and evidence affiliations. Distinguish a whole-grant aggregate from an individual project's report.
- If no report belongs to the scope, check source links and generation scope. Do not substitute an unrelated report as evidence of this project's outcomes.
- For an incorrect association, send support the page and report URLs. Check the linkage before trying to resolve it by deleting a report.