Skip to main content

Change requests

Change request overview

To correct mistakes and/or improve (an element within) a message model, users can submit change requests. An overview of all change requests can be found by selecting Community > Change requests on the menu bar.

There are four different tabs:

  • Open change requests lists all change requests that are open and have yet to be solved.
  • All change requests lists all change requests ever posted.
  • CRs from my organizations lists all change requests that have been submitted by colleagues from your own organization.
  • Create new enables users to submit a new change request.

For the first three tabs, each change requests contains the same information:

  • The identifier of the change request.
  • The title of the change request, as specified by the submitter.
  • The project to which the change request belongs. Specifications, such as message models, can be grouped within different, logical projects.
  • The submitter, identified using the account name (often an email address).
  • Checkbox indicating whether the change request is open and has to be solved, or is closed and solved already.
  • A label indicating the status of the change request.
  • The date of submission.
  • The date of the last comment being posted at the change request.

Submit a change request

To submit a new change request:

  1. In the main menu, select Community > Change requests.
  2. Select the Create new tab.
  3. Enter the title and the content of your change request.
  4. Press the Submit button.

Submit a change request at certain element

When you want to submit a new change request for a certain element, navigate to the element using the treeview and perform the following steps:

  1. Select the Change requests tab on the right panel.
  2. Enter the title and the content of your change request.
  3. Press the Submit button.

View a change request

When viewing a change request, the following information is shown:

  • The title of the change request.
  • The submitter, identified using the account name (often an email address), of the change request together with the date of submission.
  • The organizations by whom the change request is supported. This can be multiple organizations, including the organization who submitted the change request.
  • The project the change request belongs to.
  • The label indicating the status of the change request.
  • The actual content of the change request.
  • References to elements, message models, codelists or business rules, to which the change request applies and/or has an impact.
  • The proposed or final solution (dependent on whether the change request is open or closed) regarding the change request. This solution is provided by the maintainer of the model/standard.
  • A discussion panel where users can provide comments on the change request, (proposed) solution and/or suggestions made.