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

Design if-blitz command line tool #627

Closed
3 tasks
Tracked by #629
jmcook1186 opened this issue Apr 10, 2024 · 2 comments
Closed
3 tasks
Tracked by #629

Design if-blitz command line tool #627

jmcook1186 opened this issue Apr 10, 2024 · 2 comments

Comments

@jmcook1186
Copy link
Contributor

User story

As a user I want to be able to quickly test out IF in a sandbox environment. When I raise bug reports I ant to be ablke to link to an online sandbox so devs can instantly repro.

Rationale

A command line tool that will take a user's current environment and instantly replicate it in an online sandbox that can be shared with devs. This will help people to accurately report bugs, experiment with things in a safe environment, etc.

Implementation details

  • create a design document for the tool
  • share design doc with team for refinement and approval
  • create new ticket for building tool

Priority

3/5

Size

L

What does "done" look like?

design doc is approved by team

Does this require updates to documentation or other materials??

no

Deadline

tbc

@jawache
Copy link
Contributor

jawache commented Apr 14, 2024

Hey @jmcook1186 can we approach these tickets differently? It's not clear to me what a design doc is and how we are going to get clear on requirements are taken into account? At this stage we just need to make clear what the purpose of this tool is, the cli arguments and expected inputs/outputs and thinking about it that aligns to defining the acceptance criteria of the "build tool" version of the ticket.

The design tickets should be the refinement for the build tickets and specifically fleshing out the acceptance criteria section. My acceptance criteria for this tool would detail the CLI params, expected behaviour for each param, sample inputs and outputs. That's enough "design", I trust the team to build the right solution based on a clear acceptance criteria like that.

@zanete zanete moved this to Backlog in IF Apr 22, 2024
@zanete
Copy link

zanete commented Apr 22, 2024

Proposing to include the design phase as part of the workflow of #639 and closing to remove noise

@zanete zanete closed this as not planned Won't fix, can't repro, duplicate, stale Apr 22, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in IF Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants