Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a new issue form for feasibility #2298

Closed
8 of 9 tasks
Aveline-art opened this issue Sep 22, 2021 · 4 comments · Fixed by #3436
Closed
8 of 9 tasks

Create a new issue form for feasibility #2298

Aveline-art opened this issue Sep 22, 2021 · 4 comments · Fixed by #3436
Assignees
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Status: Updated No blockers and update is ready for review

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Sep 22, 2021

Overview

As a developer, we want to standardize issue templates that are repeatedly used. For this issue, we will create an issue form template for feasibility related issues.

Action Items

  • Create a feasibility-issue-template.yml file in this folder
  • This template needs the following fields:
    • Title
    • Dependency (a check box to indicate yes/no dependency, then an input for what it is if yes)
    • Overview
    • Action Items
    • Feasibility Checklist
    • Resources/Instructions
  • The resulting issue should look like this issue

Resources/Instructions

Github Forms Issue Reading
Github Forms Issue Reading Pt 2

@Aveline-art Aveline-art added role: front end Tasks for front end developers Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly labels Sep 22, 2021
@Aveline-art Aveline-art added this to New Issue Approval in Project Board via automation Sep 22, 2021
@github-actions
Copy link

Hi @Aveline-art.

Good job adding the required labels to this issue.

Just a friendly reminder to also move the issue into the "New Issue Approval" column under the Project Board. For more info on that, check Github's documentation here.
Thanks!

Additional Resources:
Wiki: How to add status labels to issues (WIP. Link will be updated when the wiki is done)
Wiki: How to create issues (WIP. Link will be updated when the wiki is done)

@macho-catt macho-catt added role: back end/devOps Tasks for back-end developers and removed role: front end Tasks for front end developers labels Oct 5, 2021
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Oct 6, 2021
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Prioritized backlog in Project Board Oct 6, 2021
@SAUMILDHANKAR SAUMILDHANKAR added the size: 1pt Can be done in 4-6 hours label Jun 18, 2022
@jdingeman jdingeman self-assigned this Jul 27, 2022
@jdingeman jdingeman moved this from Prioritized backlog to In progress (actively working) in Project Board Jul 27, 2022
@github-actions
Copy link

Hi @jdingeman, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@jdingeman
Copy link
Member

Availability: 4 hrs
ETA: EOD 7/27

@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Jul 29, 2022
Project Board automation moved this from In progress (actively working) to QA Aug 19, 2022
@HackforLABot HackforLABot moved this from QA to Done in Project Board Aug 19, 2022
@ExperimentsInHonesty ExperimentsInHonesty moved this from Done to Bonnie review in Project Board Nov 26, 2022
@ExperimentsInHonesty
Copy link
Member

@ExperimentsInHonesty ExperimentsInHonesty moved this from Bonnie review to Done in Project Board Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Status: Updated No blockers and update is ready for review
Projects
Project Board
  
Done
Development

Successfully merging a pull request may close this issue.

5 participants