You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there is an efficient way to create all the standard tickets for Base Builds? We were creating a budget for a new base build pitch (Healing Advocates Fund) and discussing the time that gets spent on every project creating all the tickets. Mike:
Might be interesting to look into look into https://github.com/gavinr/github-csv-tools as an import tool for github issues. It's somewhat limited since it doesn't appear to use an issue template, so that might be a none-starter. But if we could get that working, it would be amazing to create a tab with a list of "Required" rows with correct concatenated titles and descriptions that would jump start issue building.
Note that these wouldn't have to be only for Base Build projects! Ideally we could take this approach to the standard tickets that apply to any project.
The text was updated successfully, but these errors were encountered:
@bdimaggio I played with this concept last year for Amnesty. I converted a google sheet to github tickets using Zapier. It was mostly a common starting point, but with Base Build we probably wouldn't need to change much.
Is there is an efficient way to create all the standard tickets for Base Builds? We were creating a budget for a new base build pitch (Healing Advocates Fund) and discussing the time that gets spent on every project creating all the tickets. Mike:
Note that these wouldn't have to be only for Base Build projects! Ideally we could take this approach to the standard tickets that apply to any project.
The text was updated successfully, but these errors were encountered: