Use GitHub for a duplicate issue decision
Example: Two issues have similar titles but have failure reports in different product versions. A maintainer wants to know whether to combine them.
Keep GitHub as the source for its records. A Righthand can use available information for the decision below.
This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.
The customer task
Two issues have similar titles but have failure reports in different product versions. A maintainer wants to know whether to combine them.
Provider documentation. The documentation gives information about issue read and write operations. Repository permissions are necessary for the selected endpoint.
Make account access explicit
If GitHub is available in Connections, connect the intended account. Give the Righthand access to that connection.
Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.
For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.
Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.
The request to the Righthand
Read the two identified issues.
>
Compare version, trigger, and reported result.
>
Send differences without closing the issues.
>
Send the owner the result before 3 PM Friday.
>
Use Pacific time.
Use the provider records for the result
Identify the repository and issue before using its content. Keep the reporter's evidence and the issue state. Treat code changes and issue communication as different tasks.
Similar titles do not establish identical causes.
For a permitted write, examine the resulting account record. A proposal does not establish a completed change.
For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.
An illustrative result and next step
One report concerns CSV import. The other concerns spreadsheet upload in a later version.
The maintainer gives a decision about whether the same defect caused the two failures before giving a duplicate state.
Try one account task
- Give the Righthand one identified source record.
- Compare its result with that source.
- Examine the account record after a permitted write.
- Examine the work in Activity.
If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.
When the account tools are sufficient
Use GitHub directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.