Standard Change Requests
Raise a standard Change Request from the Create Change Request dialog, gather the documents it covers, and work it through review to release, using its Documents, Comments, and History tabs.
Overview
The standard Change Request is Lunr's original Change Request experience. You raise one from a short dialog, then work it on a page carrying Documents, Comments, and History tabs.
This page covers the standard experience from end to end. If your organisation gives you the full Change Request page instead, see Full Change Requests. Introduction to Change Requests explains which one you have and how the two differ.
Change Requests are listed on a project's Change Requests tab, described in Working in a Project.
Raising a Change Request
Select New Change Request in the Action Pane of a project's Change Requests tab. You can also raise one from the Create menu, including from the repository.
The Create Change Request dialog asks for very little. Enter a Subject, which is required, and an optional Message. Raised from outside a project, the dialog adds a Project field: search for the project, and the one you pick is confirmed below the field as Selected Project, with a Clear button to choose a different one. Create is unavailable until there is a subject, and a project where the dialog asks for one.
Any documents you have selected when you raise the request are attached to it, so selecting the documents first is the quickest way to start a request around work already in the repository. Raised from inside a project folder, the request records that folder as its own.
Selecting Create returns you to the project's Change Requests tab. Open the new request from the list to work it.
Assigning Documents to a Change Request
Documents reach a Change Request in three ways.
- Select them before raising the request, as described above.
- Upload them into the request. On the Documents tab, drag files onto the page, or use the Create menu in the Action Pane to create a document in the request. The same name-matching rules apply here as anywhere else, so an upload matching a document already in the request replaces its content, covered in Uploading Documents.
- Assign existing documents to it. Select the documents anywhere in the repository or a project, then select Assign to Change Request in the More menu.
Assign to Change Request opens a dialog naming the documents you selected. Choose the project under Assign to project, then the request under Assign to Change Request. Leave the Change Request field empty, or enter a subject that matches no existing request, and Lunr creates a request with that subject and assigns the documents to it. The dialog confirms which of the two will happen before you submit, and warns you when a document already has child documents, since proceeding creates concurrent versions of it.
Assign to Change Request is unavailable while only folders are selected. If you cannot add documents to the request you chose, a notification reads "You do not have permission to add documents to this change request."
Working a Change Request
A standard Change Request opens on its Documents tab, which lists the documents gathered under the request and carries Upload, Import Sheet, and Validate All buttons. Comments and History sit alongside it, and Checklist joins them where checklists are enabled.
The header carries the request's status badge, an On Hold badge where it applies, and who opened the request and when, above a breadcrumb back to the project and its Change Requests list.
| Action | What it does |
|---|---|
| Create | Creates a document directly in the request. |
| Request Workflow | Moves the request to its next status. It appears only where you have an action available. From the starting status, the request's creator, assignee, reviewers, and project manager can move it on. From any later status, only its reviewers can, and a request that is cancelled has no actions. A request that is complete can be moved on only by a document controller. People allowed to manage projects can take these actions whatever their role in the request. A request with validation issues offers no actions until they are resolved. If you are refused, the message reads "You don't have permission to perform this transition." |
| Place on hold, Update hold, and Resume | Reviewers can pause a request awaiting external input, change the hold, and pick the request up again, where your organisation has Change Request holds enabled. Place on hold and Update hold are hidden once the request is Complete or Cancelled, and Resume appears only while the request is on hold. |
| Release All or Release Selected | Releases the request's valid documents, all of them or only those you have selected. It is for document controllers and appears only where your organisation allows bulk release, and it is hidden once the request is Complete or Cancelled. |
| Download Package | Downloads the request's documents as a package, or only your selection where documents are selected. Where your organisation offers package options, a dialog lets you choose what to include, such as natives, renditions, the Change Request summary sheet, attachments, annotations, and xrefs. |
| Generate CR Summary | Opens a dialog of options, then exports a PDF summary of the request. |
| Share Folder | Shares a Change Request folder. It needs Change Request folders enabled and is limited to people allowed to manage projects, and stays greyed out until a folder is selected. |
Assigned To and Reviewers sit below, each listing the people currently on the request and reading "None yet" until someone is set. A control beside each heading reassigns the request or its reviewers if you are allowed to reassign work, or are the assignee or one of the reviewers.
The request's Message appears here too, shortened to a preview with Read more, and Edit where you can change it. Until there is one, it shows your organisation's message placeholder if one is set, and otherwise reads "No message provided".
Selecting documents in the list switches the lower part of the panel to batch actions covering the selection, including updating tags, transitioning documents through their own workflow, sharing, exporting, and Discard from CR.
Change Request Folders
Where your organisation enables Change Request folders, a request can hold folders of its own.
A Change Request folder starts closed, visible only to the members assigned to it rather than to everyone on the request. This is the opposite of a project folder, which starts open, so check folder membership if you expect the whole request to see a folder's documents.
Comments
Anyone who can open a Change Request can comment on it. You do not need to be its creator, its assignee, or one of its reviewers. A comment can be resolved by its author or by users allowed to resolve any comment.
Favourites
Select the star on a Change Request row to favourite it, and it appears in your favourites for quick access. A request that closes, meaning it reached Complete or Cancelled, drops out of your favourites list, though its star still shows on the request's own page so you can clear it. A rejected request is not closed and stays in the list, since it can be updated and resubmitted.
Finding Change Requests
The Change Requests tab offers a search field, a Filter button, an "Open | Closed" summary, an Export button, and a Sort dropdown. The filters cover the assignee and your Change Request tags. To see only the documents that have validation issues, use the Validation issues toggle on a request's Documents tab. Each row shows the request's number, its status and On Hold badges, and a preview of its message. Some users can delete a request from the list.
Introduction to Change Requests
Understand what a Change Request is in Lunr, how the standard and full Change Request experiences differ, and which one your organisation has given you.
Full Change Requests
Raise a Change Request on the full Change Request page, work through its reference documents by allocating new drawings and sheets or linking existing ones, and manage its folders, comments, and favourites.