05 - Fork and Merge: Contributions: creating the milestone and sending back a contribution

1. Creating the contribution Milestone from the Fork

1. The user who received the contribution did some changes in the content and at the end of their work , they will first create a Milestone.

and will get a specific message as only the annotation of the type "commen"t will be kept in the Milestone:

Note: this is specific to Milestone creation in a fork

2. The user will then get the "Add milestone window" where the type is only limited to "Contribution from Legal service" (default selected type) and "Other" :

Keeping the default choice:

will create the milestone

with the status "in preparation"

---

2. Sending the contribution Milestone from the Fork

Once the Milestone from the fork has been created, it has to be sent back to the original proposal.

In the Milestone action menu, a new action "Send contribution" is available :

Note: in this case the colors of the actions text is based on the milestone status:

When the status is not "file ready", the option is grey out :

When the status is "file ready" , the option is normal color and active :

1. Clicking on the action "Send contribution" should:

• change the status of the milestone to "Contribution sent"
• make this milestone available in the contribution pane of the original proposal.
• change the status of the sent milestone in the original proposal to "Ready to merge":

Acceptance criteria

• You can create a milestone from the fork and

  • you get the warning message about the annotation of suggestion type (see descritptio)n)
  • the title drop list are only ones defined in the description

• On this milestone of the fork,

  • the action "Send contribution" is available
  • this action can only be used when the status is "File ready" otherwise it is deactivated

• Clicking on "Send contribution" makes the contribution (milestone of the fork) available in the original proposal (contribution panel) and changes its status (see description)

Definition of done

• Contribution milestone can only have the type "Contribution from Legal Service" or "Others"
• It's not possible to send a contribution Milestone where the status is different than file ready
• On refresh of the screen the status should be updated to FILE_READY
• You cannot have suggestion annotation in a contribution milestone
• It's possible to send a contribution where the status is file ready.