Add IterationCadenceDestroy mutation

What does this MR do?

Adds IterationCadenceDestroy mutation to GQL API

Relates to #322743 (closed)

Update Boards SQL

• Query plans https://console.postgres.ai/shared/91c4d9a2-794b-483f-b699-abaf77aade83

RAW SQL

UPDATE
    "boards"
SET
    "iteration_id" = NULL
WHERE
    "boards"."iteration_id" IN (
        SELECT
            "sprints"."id"
        FROM
            "sprints"
        WHERE
            "sprints"."iterations_cadence_id" = 491)

Migration output

Migrate

== 20210419224834 UpdateIssuesIterationForeignKey: migrating ==================
-- foreign_keys(:issues)
   -> 0.0031s
-- remove_foreign_key(:issues, {:column=>:sprint_id})
   -> 0.0036s
-- transaction_open?()
   -> 0.0000s
-- foreign_keys(:issues)
   -> 0.0017s
-- execute("ALTER TABLE issues\nADD CONSTRAINT fk_3b8c72ea56\nFOREIGN KEY (sprint_id)\nREFERENCES sprints (id)\nON DELETE SET NULL\nNOT VALID;\n")
   -> 0.0014s
-- execute("SET statement_timeout TO 0")
   -> 0.0006s
-- execute("ALTER TABLE issues VALIDATE CONSTRAINT fk_3b8c72ea56;")
   -> 0.0032s
-- execute("RESET ALL")
   -> 0.0005s
== 20210419224834 UpdateIssuesIterationForeignKey: migrated (0.0234s) =========

== 20210420221106 UpdateMergeRequestsIterationForeignKey: migrating ===========
-- foreign_keys(:merge_requests)
   -> 0.0023s
-- remove_foreign_key(:merge_requests, {:column=>:sprint_id})
   -> 0.0028s
-- transaction_open?()
   -> 0.0000s
-- foreign_keys(:merge_requests)
   -> 0.0018s
-- execute("ALTER TABLE merge_requests\nADD CONSTRAINT fk_7e85395a64\nFOREIGN KEY (sprint_id)\nREFERENCES sprints (id)\nON DELETE SET NULL\nNOT VALID;\n")
   -> 0.0018s
-- execute("ALTER TABLE merge_requests VALIDATE CONSTRAINT fk_7e85395a64;")
   -> 0.0028s
== 20210420221106 UpdateMergeRequestsIterationForeignKey: migrated (0.0183s) ==

Rollback

== 20210420221106 UpdateMergeRequestsIterationForeignKey: reverting ===========
-- foreign_keys(:merge_requests)
   -> 0.0028s
-- remove_foreign_key(:merge_requests, {:column=>:sprint_id})
   -> 0.0030s
-- transaction_open?()
   -> 0.0000s
-- foreign_keys(:merge_requests)
   -> 0.0020s
-- execute("ALTER TABLE merge_requests\nADD CONSTRAINT fk_7e85395a64\nFOREIGN KEY (sprint_id)\nREFERENCES sprints (id)\nON DELETE CASCADE\nNOT VALID;\n")
   -> 0.0015s
-- execute("SET statement_timeout TO 0")
   -> 0.0006s
-- execute("ALTER TABLE merge_requests VALIDATE CONSTRAINT fk_7e85395a64;")
   -> 0.0038s
-- execute("RESET ALL")
   -> 0.0006s
== 20210420221106 UpdateMergeRequestsIterationForeignKey: reverted (0.0231s) ==

== 20210419224834 UpdateIssuesIterationForeignKey: reverting ==================
-- foreign_keys(:issues)
   -> 0.0018s
-- remove_foreign_key(:issues, {:column=>:sprint_id})
   -> 0.0026s
-- transaction_open?()
   -> 0.0000s
-- foreign_keys(:issues)
   -> 0.0016s
-- execute("ALTER TABLE issues\nADD CONSTRAINT fk_3b8c72ea56\nFOREIGN KEY (sprint_id)\nREFERENCES sprints (id)\nON DELETE CASCADE\nNOT VALID;\n")
   -> 0.0010s
-- execute("ALTER TABLE issues VALIDATE CONSTRAINT fk_3b8c72ea56;")
   -> 0.0023s
== 20210419224834 UpdateIssuesIterationForeignKey: reverted (0.0162s) =========

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • [-] I have not included a changelog entry because _____.
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Related to #322743 (closed)

Auto-Summary 🤖

Discoto Usage

---

Points

Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive) point:. For example, the following are all valid points:

• #### POINT: This is a point
• * point: This is a point
• + Point: This is a point
• - pOINT: This is a point
• point: This is a **point**

Note that any markdown used in the point text will also be propagated into the topic summaries.

Topics

Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.

Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive) topic:. For example, the following are all valid topics:

• # Topic: Inline discussion topic 1
• ## TOPIC: **{+A Green, bolded topic+}**
• ### tOpIc: Another topic

Quick Actions

Action	Description
/discuss sub-topic TITLE	Create an issue for a sub-topic. Does not work in epics
/discuss link ISSUABLE-LINK	Link an issuable as a child of this discussion

---

Last updated by this job

Discoto Settings

---
summary:
  max_items: -1
  sort_by: created
  sort_direction: ascending

See the settings schema for details.