diff --git a/feps/fep-a4ed.md b/feps/fep-a4ed.md
index 7c8e24c..70cd8ba 100644
--- a/feps/fep-a4ed.md
+++ b/feps/fep-a4ed.md
@@ -59,12 +59,11 @@ Following metadata key-value pairs may be placed at the top of a proposal:
 - `dateReceived`: Date of when the proposal was added to the repository (when status is set to `DRAFT`).
 - `dateWithdrawn`: Date of when the proposal status was set to `WITHDRAWN` (only for proposals with status `WITHDRAWN`).
 - `dateFinalized`: Date of when the proposal status was set to `FINAL` (only for proposals with status `FINAL`).
+- `discussionsTo`: Link to the tracking issue for the proposal.
 - `relatedFeps`: A comma separated list of related FEPs (e.g. `FEP-a4ed, FEP-141a, FEP-686f`).
 - `replaces`: A comma separated list of FEPs that are replaced by the proposal.
 - `replacedBy`: Identifier of a FEP that replaces the proposal.
 
-Future FEPs may specify additional metadata fields.
-
 ### Required Sections
 
 Every FEP should include at least the following sections:
@@ -101,7 +100,7 @@ Fediverse Enhancement Proposals must be placed in the public domain by the autho
 
 1. A Fediverse Enhancement Proposal can be submitted by individuals or groups of individuals (authors). See the `SUBMISSION.md` file for a list of accepted submission methods.
 2. Within seven days one of the editors will read and respond to the proposal. The editor checks if the proposal conforms to the required structure and fits the scope and objective of the FEPs. The editor may request the authors to clarify, justify, or withdraw the proposal. Such a request must not reflect the personal bias of an editor. Rather, it will be made strictly to maintain a high quality of submissions. The editors reserve the right to reject a submission when a proposal amounts to blatant misuse of the process. The authors may seek feedback from the wider community if the submitted proposal is rejected or clarifications are requested.
-3. If a FEP editor approves a submission it receives the status `DRAFT` and is added to the repository.
+3. If a FEP editor approves a submission it receives the status `DRAFT` and is added to the repository. Editor also creates a tracking issue for the proposal.
 4. While a proposal has the status `DRAFT`:
    - Authors are responsible for initiating community discussion and collecting feedback.
    - Authors may submit updates to the proposal which will be checked in to the repository by an editor.