• 65
    • 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
    • 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.

      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.

        1. dont-f-the-customer.png
          dont-f-the-customer.png
          30 kB
        2. image-2016-11-30-17-09-04-940.png
          image-2016-11-30-17-09-04-940.png
          19 kB
        3. JRA-5783.png
          JRA-5783.png
          44 kB

            [JRASERVER-5783] Make field required only for one state transition

            Can it be done without a plugin?? 

            Eloy García added a comment - Can it be done without a plugin?? 

            @Jira It is becoming a real pain that every time I need a feature it is only available through a pay option. I consider we pay enough already with the subscription to have what I consider VERY basic functionality and I see that your product is becoming clumsier and less and less admin/user friendly with every new half backed feature you add and WE need to debug while paying our licenses.

            Really, it's probably not the first time I write, but if not for the complexity of moving to another solution provider, I would definitely think about it. 

            Back to this topic:

            Why can't we just clone the resolution field and have this behavior for other fields as well???

            Bernard Clabots added a comment - @Jira It is becoming a real pain that every time I need a feature it is only available through a pay option. I consider we pay enough already with the subscription to have what I consider VERY basic functionality and I see that your product is becoming clumsier and less and less admin/user friendly with every new half backed feature you add and WE need to debug while paying our licenses. Really, it's probably not the first time I write, but if not for the complexity of moving to another solution provider, I would definitely think about it.  Back to this topic: Why can't we just clone the resolution field and have this behavior for other fields as well???

            I totally agree with @Joel Cairney and @Sumit Pandya! 

            Alexander Hendler added a comment - I totally agree with @Joel Cairney and @Sumit Pandya! 

            I Agree with @Joel Cairney. If it is available in Jira cloud then why Server users have to pay extra. This should be considered as basic feature from Atlassian. Similarly I want to mandate "Reviewer" custom-field, for every "Resolve Issue" transition, but the Jira is unable to fulfill this basic requirement.

            In my opinion Atlassian is unable to understand the Product Management now-a-days. I'm unusually paying hefty mount on their Marketplace. Their integral user licensing policy is cynical, for example We have small team of 5 QA who uses Zephyr plugin, but I've to pay charge for whopping 50-user license.

            Sumit Pandya added a comment - I Agree with @Joel Cairney. If it is available in Jira cloud then why Server users have to pay extra. This should be considered as basic feature from Atlassian. Similarly I want to mandate "Reviewer" custom-field, for every "Resolve Issue" transition, but the Jira is unable to fulfill this basic requirement. In my opinion Atlassian is unable to understand the Product Management now-a-days. I'm unusually paying hefty mount on their Marketplace. Their integral user licensing policy is cynical, for example We have small team of 5 QA who uses Zephyr plugin, but I've to pay charge for whopping 50-user license.

            This is a basic part of TFS bug tracker functionality since 2005.  It's even supported in Jira Cloud!  Why do SERVER users have to pay extra for it?  It should be part of the base feature package.  Please re-open.

            Joel Cairney added a comment - This is a basic part of TFS bug tracker functionality since 2005.  It's even supported in Jira Cloud!  Why do SERVER users have to pay extra for it?  It should be part of the base feature package.  Please re-open.

            can we achieve this without installing plugin ?

             

            #Uday Kiran added a comment - can we achieve this without installing plugin ?  

            All I need is enabling Fields during Workflow transitions, this seems so simple and asking us to pay $450 for an entire suite seems unreasonable.

            Deleted Account (Inactive) added a comment - All I need is enabling Fields during Workflow transitions, this seems so simple and asking us to pay $450 for an entire suite seems unreasonable.

            I might suggest folks go upvote this issue
            https://jira.atlassian.com/browse/JRASERVER-5783

            Kimberly Deal [Columbus ACE] added a comment - I might suggest folks go upvote this issue https://jira.atlassian.com/browse/JRASERVER-5783

            Sean M added a comment -

            When I create radio buttons, I automatically get an unwanted 'None' option. I was told that the way to get rid of the None option is to make the field required. How, then, do I get rid of the None option while utilizing the accepted workaround for this issue?

            Sean M added a comment - When I create radio buttons, I automatically get an unwanted 'None' option. I was told that the way to get rid of the None option is to make the field required. How, then, do I get rid of the None option while utilizing the accepted workaround for this issue?

            Unfortunately the new Validator was provided to Cloud customers and Atlassian punted this Server ticket – Immediately after that the JSU plugin was made paid. So all around the situation has left me and the 800+ customers, as Atlassian would say ...

            Steven F Behnke added a comment - Unfortunately the new Validator was provided to Cloud customers and Atlassian punted this Server ticket – Immediately after that the JSU plugin was made paid. So all around the situation has left me and the 800+ customers, as Atlassian would say ...

              Unassigned Unassigned
              9f222f87c041 Furore Jira Admin
              Votes:
              815 Vote for this issue
              Watchers:
              491 Start watching this issue

                Created:
                Updated:
                Resolved: