lotus/.github/ISSUE_TEMPLATE/m1_bug_report_deal.yml

name: "M1 Bug Report For Deal Making"
description: "File a bug report around deal making for the M1 releases"
labels: [need/triage, kind/bug, M1-release]
body:
- type: checkboxes
  id: checklist
  attributes:
    label: Checklist
    description: Please check off the following boxes before continuing to file a bug report!
    options:
      - label: This is **not** a question or a support request. If you have any lotus related questions, please ask in the [lotus forum](https://github.com/filecoin-project/lotus/discussions).
        required: true
      - label: I **am** reporting a bug w.r.t one of the [M1 tags](https://github.com/filecoin-project/lotus/discussions/6852#discussioncomment-1043951). If not, choose another issue option [here](https://github.com/filecoin-project/lotus/issues/new/choose).
        required: true
      - label: I **am** reporting a bug around deal making. If not, create a [M1 Bug Report For Non Deal Making Issue](https://github.com/filecoin-project/lotus/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Fbug%2CM1-release&template=m1_bug_report_non_deal.yml).
        required: true
      - label: I have my log level set as instructed [here](https://github.com/filecoin-project/lotus/discussions/6852#discussioncomment-1043678) and have logs available for troubleshooting.
        required: true
      - label: The deal is coming from one of the M1 clients(communitcated in the coordination slack channel).
        required: true
      - label: I **have** searched on the [issue tracker](https://github.com/filecoin-project/lotus/issues) and the [lotus forum](https://github.com/filecoin-project/lotus/discussions), and there is no existing related issue or discussion.
        required: true
- type: dropdown 
  id: lotus-componets
  validations:
    required: true
  attributes:
    label: Lotus Component
    description: Please select the lotus component you are filing a bug for
    options:
    - lotus miner market subsystem - storage deal
    - lotus miner market subsystem - retrieval deal
    - lotus miner - storage deal
    - lotus miner - retrieval deal
- type: textarea
  id: version
  attributes:
    label: Lotus Tag and  Version
    description: Enter the  lotus tag, output of `lotus version` and `lotus-miner version`.
  validations:
    reuiqred: true
- type: textarea
  id: Description
  attributes:
    label: Describe the Bug
    description: |
      This is where you get to tell us what went wrong, when doing so, please try to provide a clear and concise description of the bug with all related information:
      * What you were doding when you experienced the bug?
      * Any *error* messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
      * What is the expected behaviour?
    render: bash
  validations:
    required: true
- type: textarea
  id: deal-status
  attributes:
    label: Deal Status
    description: What's the status of the deal?
    placeholder: |
      Please share the output of `lotus-miner storage-deals|retrieval-deals list [-v]` commands for the deal(s) in question.
  validations:
    required: true
- type: textarea
  id: data-transfer-status
  attributes:
    label: Data Transfer Status
    description: What's the status of the data transfer?
    placeholder: |
      Please share the output of `lotus-miner data-transfers list -v` commands for the deal(s) in question.
  validations:
    required: true
- type: textarea
  id: logging
  attributes:
    label: Logging Information
    description: Please link to the whole of the miner logs on your side of the transaction. You can upload the logs to a [gist](https://gist.github.com).
  validations:
    required: true
- type: textarea
  id: RepoSteps
  attributes:
    label: Repo Steps (optional)
    description: "Steps to reproduce the behavior"
    value: |
      1. Run '...'
      2. Do '...'
      3. See error '...'
      ...
    render: bash
  validations:
    required: false