Write effective requests (Beta)
The Assistant works best when your request identifies the engineering context, desired outcome, relevant context, and boundaries.
What to include | What to provide | Example |
|---|---|---|
Identify the Jama Connect content | Name the items, set, folder, or other Jama Connect content that the Assistant should use. Include a document key or item ID when it helps remove ambiguity. | Instead of: Copy the requirements Try: Create copies of all Items in folder FLD-3 and place the copies in folder FLD-42. |
Describe the outcome | Explain what you want the Assistant to produce or change. Distinguish between similar operations, such as copying Items, reusing Items, or duplicating a Folder. | For example: Copy every item contained in folder FLD-3 into folder FLD-42. Do not copy the folder itself. |
Provide context | If the result must follow a particular structure or style, identify an existing Jama Connect item that the Assistant can use as a source. | For example: Propose five new requirements for this Set. Use the Description field of SYS-102 as the template for each proposal. When relevant, include the intended engineering domain, conditions, or constraints: Propose five requirements related to Android device battery-temperature risks. Follow the structure of SYS-102. |
Specify how to handle misinformation | Tell the Assistant what to do when a required value isn’t available in Jama Connect. | For example: Do not invent performance thresholds or operating conditions. Preserve missing information as a clearly labeled placeholder. Or: If a required value can't be verified from the selected Items, ask me for it before continuing. This helps keep proposed content grounded in the engineering record. |
Work with a focused set of content | For analysis or comparison, identify a manageable set of items and the fields that matter. | Instead of: Find duplicates in the project. Try: Retrieve the 20 requirements in Folder FLD-3 and display their Name and Description in a table. Then identify Items that may cover similar requirements and explain why. |
Note
Focused requests produce results that are easier to review, validate, and act on. For project-wide reporting or large data sets, Jama Connect exports, reports, APIs, or a purpose-built workflow when appropriate.