Worked example for Customizable internal request tracker
This customizable internal request tracker example page covers customizable internal request tracker source. First, choose one small task you can check by hand. Then follow the steps below and compare the result with your source information.
The download is a runnable portal + offline workspace. This page explains one part of its use. For the full process, follow the ten linked guides in order or open the section you need. Keep your source notes with your working files.
A repeatable practice exercise
The package includes example-backup.json. Use the instructions for this file and the example controls in the workspace; keep the supplied file unchanged so you can repeat the exercise.
This exercise is for customizable internal request tracker source; all practice names, values and records should be fictional. The aim is to understand the supplied workflow before entering real information.
Build a small test case
- Check Request title: give the practice item a recognizable reference such as Practice A.
- Review Requested by: enter a short fictional value that you can recognize in the output.
- Confirm Details: enter a short fictional value that you can recognize in the output.
- Check Assigned owner: enter a short fictional value that you can recognize in the output.
- Review Due date: choose a clearly recorded practice date or period.
- Confirm Status: enter a short fictional value that you can recognize in the output.
Change one thing and compare
Make one small edit and compare the result with the original. Check that the intended item changed and that unrelated information stayed intact.
Keep your practice results separate from your live work. If the result is unexpected, use the troubleshooting guide and the instructions in the ZIP before continuing.
Keep a practice log
First, record your starting inputs in a separate note. Include the units, dates and references that apply. Next, write down the result you expect. This makes the test useful even if you return to it later.
After that, change one value or one piece of text. Compare the old and new results. If several things change at once, repeat the test with a smaller edit. Finally, remove the practice data before you start real work.
Details to check in this product
- Request title: confirm the source and keep a clear reference.
- Requested by: check the value against your practice case.
- Details: review the result before you save or share it.
- Assigned owner: confirm the source and keep a clear reference.
- Due date: check the value against your practice case.
- Status: review the result before you save or share it.
A useful reference
Use an isolated environment when following the runnable application setup. Read the Python documentation on virtual environments for more detail.