Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Fix
Fix Version/s: None
Component/s: Administration - Workflows, Project Administration - Permissions
Labels:
- affects-cloud
- affects-server
- jw-platform
- pm_status
- sic
- sic-fields
- wl

Support reference count:
65
Current Status:

Hide

Atlassian Update – 8th December 2017

Hi all,

Thank you for commenting on this issue. Suggested functionality is available by installing the JIRA Suite Utilities plugin, which is available on the Atlassian Marketplace.

Suite Utilities for Jira used to be a free app/add-on until recently, and we realise that many Jira users considered its capabalities an integral part of Jira.

The decision to commercialize the app was made by the vendor. As soon as we learned about this change, we notified our users so you could plan accordingly.

We understand your frustration and we will share your feedback to the vendor. Ultimately though, it is the vendor's choice in terms of how they price their apps on the Atlassian Marketplace.

As you know, Jira is a platform that anyone can build on, and the Atlassian Marketplace is a key part of what makes Jira so powerful.

As the Jira Server Team, we prioritize investments that impact the majority of our customers. We belive Suite Utilities for Jira deliveres great value to our customers and the plugin has proven to do it's job well. This is why we currently have no plans to implements JSU's finctionalities in the core product.

Also please remember that the first version of the plugin developed by Atlassian Labs is still open source.

Feel free to reach out to me with any questions.

Gosia Kowalska
Senior Product Manager Jira Server

Show
Atlassian Update – 8th December 2017 Hi all, Thank you for commenting on this issue. Suggested functionality is available by installing the JIRA Suite Utilities plugin, which is available on the Atlassian Marketplace . Suite Utilities for Jira used to be a free app/add-on until recently, and we realise that many Jira users considered its capabalities an integral part of Jira. The decision to commercialize the app was made by the vendor. As soon as we learned about this change, we notified our users so you could plan accordingly. We understand your frustration and we will share your feedback to the vendor. Ultimately though, it is the vendor's choice in terms of how they price their apps on the Atlassian Marketplace. As you know, Jira is a platform that anyone can build on, and the Atlassian Marketplace is a key part of what makes Jira so powerful. As the Jira Server Team, we prioritize investments that impact the majority of our customers. We belive Suite Utilities for Jira deliveres great value to our customers and the plugin has proven to do it's job well. This is why we currently have no plans to implements JSU's finctionalities in the core product. Also please remember that the first version of the plugin developed by Atlassian Labs is still open source . Feel free to reach out to me with any questions. Gosia Kowalska Senior Product Manager Jira Server
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

Original request description:

The reporter can not add an issue when he has no resolve permissions and the "fixed Version" field is a required field.

As a JIRA Administrator I want a "Fixed version" to be a required field when resolving. But it seems illogical that someone reporting an issue should enter the field. This applies to other fields as well.

Workaround

The JIRA Suite Utilities provides a fields required validator that can be configured to set fields required on specific transitions.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

dont-f-the-customer.png
30 kB
20/Mar/2018 11:24 PM
image-2016-11-30-17-09-04-940.png
19 kB
30/Nov/2016 10:09 PM
JRA-5783.png
44 kB
18/Sep/2007 9:03 PM

Issue Links

is duplicated by

JRASERVER-10847 Fields marked required are required on screens that don't provide them

Closed

JRASERVER-15956 Resolution field needs to be required

Closed

JRASERVER-15977 CLONE -Resolution field needs to be required

Closed

JRASERVER-19183 some required fields should only be required for specific screens

Closed

JRASERVER-6549 Allow to make fields required on per screen/workflow step basis

Closed

JRASERVER-13668 Would like to be able to mark certain fields required on SOME screens, not all screens

Closed

JRASERVER-14572 Cannot make Original Estimate Field required

Closed

JRASERVER-20145 Required Fields on Workflow-transition

Closed

JRASERVER-28199 Mandatory Field only on specific status values

Closed

JRASERVER-45618 Allow no or null values in radio buttons & single select fields

Closed

is related to

JRASERVER-9844 Validators silently break Bulk Transition

Closed

JRASERVER-9931 Failing validators during bulk transition cause index to be updated incorrectly

Closed

JRASERVER-11125 JIRA 4.0 Enterprise Requirements

Closed

JRASERVER-13667 Make field required per issue status

Closed

JRASERVER-12773 Provide a custom field required without a "none" option on the resolve screen

Gathering Interest

relates to

JRASERVER-8100 Exception thrown by validate() method of custom Validator handled as a server error

Closed

JRASERVER-15335 Remote API Interface doesn't enforce Resolution Setting

Closed

JRACLOUD-5783 Make field required only for one state transition

Closed

JRASERVER-2372 It would be nice to have an option to hide fields in 'Create issue' phase

Closed

JRASERVER-3417 Hiding issue fields for some users /user groups

Closed

JRASERVER-9088 Create a workflow validator to require a field on workflow transition

Closed

was cloned as

JRASERVER-65813 Make field required only for one state transition

Gathering Interest

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...

(5 is duplicated by, 5 is related to, 6 relates to, 1 was cloned as, 17 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Furore Jira Admin

Votes:: 815 Vote for this issue

Watchers:: 489 Start watching this issue

Dates

Created:: 28/Jan/2005 12:43 PM

Updated:: 28/Nov/2023 12:41 PM

Resolved:: 08/Dec/2017 9:41 AM