| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
We do not store the passwords, only user keys and time are stored. The data is stored in the Jira database. Here is the example:
| ID | ISSUE | CUSTOMFIELD | PARENTKEY | STRINGVALUE | NUMBERVALUE | TEXTVALUE | DATEVALUE | VALUETYPE | UPDATED |
|---|---|---|---|---|---|---|---|---|---|
| 10000 | 10100 | 10100 | null | \\{"username":"admin","time":1538481863970,"issueKey":"TEST-7"} | null | null | null | null | 1538481863988 |
How should I provide user credentials in JSD?
...
We're working hard to ensure the most similar functionality in Cloud as you're used to seeing in Server. But it may not be totally the same due to different architecture between Server and Cloud Jira versions.
Feature | Server/DC | Cloud | Note |
|---|---|---|---|
Prevents unauthorized actions on tickets |  | | |
| Exception for Signing an Issue | |  | Scheduled |
Requiring Electronic Signatures on ticket transition screen | | | This functionality is not relevant in Cloud |
| Bulk operation with Electronic Signatures | | | Scheduled |
| Signature information tab | | | |
| Сheck user credentials before the transition is performed (ES Validator) | | | |
| | Investigating feasibility | |
| JQL functions | | | Investigating feasibility |
| |