Data Stored in Jira
- Andreas Schmidt
- Tobias Viehweger
We do use different entities to store information in Jira itself.
App Properties
We store all settings made by the admin as app properties. This includes settings and templates.
Issue Properties
When creating or updating an issue, we store additional information at the issue itself as issue properties. The key is always yasoon-outlook-email-data
We use these information to query the related issues in the Outlook addin sidebar and show possible duplicate tickets. You can also use them in JQL yourself.
Name | Alias in JQL | Description |
|---|---|---|
id | createdByEmailId | the id of the email that has been used to create the issue |
conversationId | createdByEmailConversationId | conversation Id that has been used to create the issue |
receiverEmail | createdByEmailReceiver | emails addresses of the recipients that were used to create the issue |
emailSender | createdByEmailSender | email address of the sender that was used to create the issue |
involvedEmailAddresses | involvedEmailAddresses | All email addresses that were involved into the issue. Also includes add-to-issue |
involvedEmailIds | involvedEmailIds | All email Ids that are related to this issue |
involvedEmailConversationIds | involvedEmailConversationIds | All conversation IDs that are related to this issue |
User Properties
We store a user property yasoon-user-guid with a randomly generated guid to correctly identify recurring users.