...
In addition to this, we solved a couple of bugs related to Jira 7.10 compatibility:
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 14c546bb-3a07-399f-9d5b-ade2eafb3ae3 |
|---|
| key | DADMIN-425 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 14c546bb-3a07-399f-9d5b-ade2eafb3ae3 |
|---|
| key | DADMIN-424 |
|---|
|
As well as fixed an issue where the project administrator could add the same transition multiple times:
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 14c546bb-3a07-399f-9d5b-ade2eafb3ae3 |
|---|
| key | DADMIN-420 |
|---|
|
...
...
...