-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate issuelinktype.linkname values by performing direct SQL insert or update statements.
It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail.
Suggested Solution
Please add a unique constrain on the linkname column of the issuelinktype table.
Additional Comments
- Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API.
- The described problem was found in Jira 8.5 and it is expected to be also present in previous Jira versions.
issuelinktype table description:
Table "public.issuelinktype"
Column | Type | Modifiers
----------+------------------------+-----------
id | numeric(18,0) | not null
linkname | character varying(255) |
inward | character varying(255) |
outward | character varying(255) |
pstyle | character varying(60) |
Indexes:
"pk_issuelinktype" PRIMARY KEY, btree (id)
"linktypename" btree (linkname)
"linktypestyle" btree (pstyle)
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-71773] Add a unique constraint to the issuelinktype table
| UIS | Original: 1 | New: 0 |
| UIS | Original: 0 | New: 1 |
| UIS | Original: 1 | New: 0 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 633506 ] |
| UIS | New: 1 |
| Description |
Original:
h3. Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate {{issuelinktype.linkname}} values by performing direct SQL insert or update statements. It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail. h3. Suggested Solution Please add a unique constrain on the {{linkname}} column of the {{issuelinktype}} table. \\ *Additional Comments* * Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API. * The described problem was found in Jira 8.5 and it is expected to be also present in previous Jira versions. |
New:
h3. Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate {{issuelinktype.linkname}} values by performing direct SQL insert or update statements. It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail. h3. Suggested Solution Please add a unique constrain on the {{linkname}} column of the {{issuelinktype}} table. \\ *Additional Comments* * Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API. * The described problem was found in Jira 8.5 and it is expected to be also present in previous Jira versions. {{issuelinktype}} table description: {noformat} Table "public.issuelinktype" Column | Type | Modifiers ----------+------------------------+----------- id | numeric(18,0) | not null linkname | character varying(255) | inward | character varying(255) | outward | character varying(255) | pstyle | character varying(60) | Indexes: "pk_issuelinktype" PRIMARY KEY, btree (id) "linktypename" btree (linkname) "linktypestyle" btree (pstyle) {noformat} |
| Labels | Original: database | New: database database-index |
| Description |
Original:
h3. Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate {{issuelinktype.linkname}} values by performing direct SQL insert or update statements. It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail. h3. Suggested Solution Please add a unique constrain on the {{linkname}} column of the {{issuelinktype}} table. \\ *Additional Comment* Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API. |
New:
h3. Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate {{issuelinktype.linkname}} values by performing direct SQL insert or update statements. It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail. h3. Suggested Solution Please add a unique constrain on the {{linkname}} column of the {{issuelinktype}} table. \\ *Additional Comments* * Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API. * The described problem was found in Jira 8.5 and it is expected to be also present in previous Jira versions. |
| Description |
Original:
h3. Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate {{issuelinktype.linkname}} values by performing direct SQL insert or update statements. It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail. h3. Suggested Solution Please add a unique constrain on the {{linkname}} column of the {{issuelinktype}} table. *Additional Comment* Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API. |
New:
h3. Problem Definition
The Jira application does not allow to add duplicate values to the name of an issuelinktype (linkname column) through the Jira user interface nor through the Jira REST API. However it is still possible to add duplicate {{issuelinktype.linkname}} values by performing direct SQL insert or update statements. It is important to note that having duplicate issuelinktype names (issuelinktype.linkname) can cause some operations such as exporting issues to CSV files to fail. h3. Suggested Solution Please add a unique constrain on the {{linkname}} column of the {{issuelinktype}} table. \\ *Additional Comment* Please note that this suggestions aims to keep consistency with the approach already taken in the Jira aplication and enforced in the Jira user interface and REST API. |
| Labels | New: database |