• Type: Suggestion
• Resolution: Unresolved
• Component/s: Issue - View (Internal developer use only)
• Labels:

  None

[JRACLOUD-61183] Custom Field value defined by JQL

Matthew Hunter made changes - 08/Jan/2024 1:30 PM

Remote Link

New: This issue links to "Page (Confluence)" [ 853024 ]

SET Analytics Bot made changes - 28/Dec/2023 4:01 AM

Support reference count

Original: 8

New: 9

SET Analytics Bot made changes - 10/Nov/2022 4:02 AM

Support reference count

Original: 7

New: 8

SET Analytics Bot made changes - 22/Oct/2022 4:01 AM

Support reference count

Original: 6

New: 7

SET Analytics Bot made changes - 02/Aug/2022 4:01 AM

Support reference count

Original: 5

New: 6

SET Analytics Bot made changes - 12/Apr/2022 4:01 AM

Support reference count

New: 5

SET Analytics Bot made changes - 05/Jan/2022 3:01 AM

UIS

Original: 12

New: 0

SET Analytics Bot made changes - 22/Dec/2021 2:29 AM

UIS

New: 12

Petter Gonçalves made changes - 15/Nov/2019 6:42 PM

Description

Original: {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-61183]. {panel} h4. PROBLEM:  * One critical feature/functionality that is missing in JIRA is the ability to define a custom field based on a JQL. This is useful to seamlessly integrate different projects/processes within JIRA. Example: A select-field (or auto-complete, etc.) that its values are based on the issues from Project X with Status Y (this is defined via a JQL). h4. SUGGESTION:  * It would be great if this feature becomes native in JIRA. h4. Workaround:  * The following third party apps provide this feature for Jira on-premise, a valid option would be to contact their support team and verify if they consider providing the same app on the Cloud:  ** [JQL Issue Select|https://marketplace.atlassian.com/apps/1213338/jql-issue-select].  ** [Elements Connect - formerly nFeed|https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=server&tab=overview]  ** [Query Issues Custom fields|[https://marketplace.atlassian.com/apps/1211009/query-issues-custom-fields?hosting=server&tab=overview]] (This one is a free app)

New: {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-61183]. {panel} h4. PROBLEM:  * One critical feature/functionality that is missing in JIRA is the ability to define a custom field based on a JQL. This is useful to seamlessly integrate different projects/processes within JIRA. Example: A select-field (or auto-complete, etc.) that its values are based on the issues from Project X with Status Y (this is defined via a JQL). h4. SUGGESTION:  * It would be great if this feature becomes native in JIRA. h4. Workaround:  * The following third party apps provide this feature for Jira on-premise, a valid option would be to contact their support team and verify if they consider providing the same app on the Cloud:  ** [JQL Issue Select|https://marketplace.atlassian.com/apps/1213338/jql-issue-select].  ** [Elements Connect - formerly nFeed|https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=server&tab=overview]  ** [Query Issues Custom fields|https://marketplace.atlassian.com/apps/1211009/query-issues-custom-fields?hosting=server&tab=overview] (This one is a free app)

Petter Gonçalves made changes - 15/Nov/2019 6:42 PM

Description

Original: {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-61183]. {panel} h4. PROBLEM:  * One critical feature/functionality that is missing in JIRA is the ability to define a custom field based on a JQL. This is useful to seamlessly integrate different projects/processes within JIRA. Example: A select-field (or auto-complete, etc.) that its values are based on the issues from Project X with Status Y (this is defined via a JQL). h4. SUGGESTION:  * It would be great if this feature becomes native in JIRA. h4. Workaround:  * The following third party apps provide this feature for Jira on-premise, a valid option would be to contact their support team and verify if they consider providing the same app on the Cloud:  ** [JQL Issue Select|https://marketplace.atlassian.com/apps/1213338/jql-issue-select].  ** [Elements Connect - formerly nFeed|https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=server&tab=overview]  ** [Query Issues Custom fields|[https://marketplace.atlassian.com/apps/1211009/query-issues-custom-fields?hosting=server&tab=overview]] (This one is a free app)

New: {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-61183]. {panel} h4. PROBLEM:  * One critical feature/functionality that is missing in JIRA is the ability to define a custom field based on a JQL. This is useful to seamlessly integrate different projects/processes within JIRA. Example: A select-field (or auto-complete, etc.) that its values are based on the issues from Project X with Status Y (this is defined via a JQL). h4. SUGGESTION:  * It would be great if this feature becomes native in JIRA. h4. Workaround:  * The following third party apps provide this feature for Jira on-premise, a valid option would be to contact their support team and verify if they consider providing the same app on the Cloud:  ** [JQL Issue Select|https://marketplace.atlassian.com/apps/1213338/jql-issue-select].  ** [Elements Connect - formerly nFeed|https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=server&tab=overview]  ** [Query Issues Custom fields|[https://marketplace.atlassian.com/apps/1211009/query-issues-custom-fields?hosting=server&tab=overview]] (This one is a free app)

Load more older events