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

      Atlassian Update – 4 October 2016

      Hi everyone,

      We will not be bundling new third-party plugins in JIRA Cloud. Most third-party plugins that were previously bundled have been migrated to new versions built on Atlassian Connect. We expect to complete this in the near future.

      Adaptavist has already released ScriptRunner for JIRA Cloud. Check it out on the Atlassian Marketplace.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Senior Product Manager, JIRA

            [JRASERVER-41869] Bundle Script Runner Plugin into OnDemand

            King MCMS added a comment -

            King MCMS added a comment - https://open.spotify.com/artist/4PygJ8LPvOSVEZZN2JgL2r?si=bxr2--5QRLu6K91OnNcY9w&dl_branch=1

            King MCMS added a comment -

             

            King MCMS added a comment -  

            Thanks Christian,

            Currently, we don't have a solution that allows us to implement ScriptRunner behaviours functionality in the Cloud but please feel free to watch our add-on in the Marketplace releases for updates.

            regards, Mark.

            Mark McCormack (Adaptavist) added a comment - Thanks Christian, Currently, we don't have a solution that allows us to implement ScriptRunner behaviours functionality in the Cloud but please feel free to watch our add-on in the Marketplace releases  for updates. regards, Mark.

            Hello,

            The main feature I am looking for is the ability to hide certain fields from certain users / groups. We currently collaborate using Jira with our clients and do not want them seeing time tracking. The inability to hide fields from users / groups has caused us not to use the time tracking feature in Jira for certain projects which has been a real pain. Hopefully, you can provide a solution to this problem (within scriptrunner) soon.

            Thanks

            Christian Slaviero added a comment - Hello, The main feature I am looking for is the ability to hide certain fields from certain users / groups. We currently collaborate using Jira with our clients and do not want them seeing time tracking. The inability to hide fields from users / groups has caused us not to use the time tracking feature in Jira for certain projects which has been a real pain. Hopefully, you can provide a solution to this problem (within scriptrunner) soon. Thanks

            Dave Meyer added a comment -

            Hi guys,

            From the JIRA side, we are investing heavily in API improvements and features to help our partners like Adaptavist make their add-ons for JIRA Cloud as feature-rich as possible. We recognize that the 1.0 of many add-ons is likely not to have parity with existing add-ons for JIRA Server. And the reality is that it will almost always be possible to do more with plugins that run in-process in JIRA and have unlimited access to internal methods than is possible with asynchronous services communicating over REST APIs.

            Our goal with JIRA Cloud is to offer the most extensible service possible (and I believe we are already a market leader in this regard) and supplement gaps with improvements to native functionality elsewhere. For example, in the last few months we have released native support for the following workflow conditions and validators:

            • Previous status Condition
            • Separation of Duties Condition
            • Hide transition from user Condition
            • Field has been modified Validator
            • Field required Validator, which also includes comments
            • Field has single value Validator
            • Previous state Validator
            • Parent status Validator

            Dave Meyer added a comment - Hi guys, From the JIRA side, we are investing heavily in API improvements and features to help our partners like Adaptavist make their add-ons for JIRA Cloud as feature-rich as possible. We recognize that the 1.0 of many add-ons is likely not to have parity with existing add-ons for JIRA Server. And the reality is that it will almost always be possible to do more with plugins that run in-process in JIRA and have unlimited access to internal methods than is possible with asynchronous services communicating over REST APIs. Our goal with JIRA Cloud is to offer the most extensible service possible (and I believe we are already a market leader in this regard) and supplement gaps with improvements to native functionality elsewhere. For example, in the last few months we have released native support for the following workflow conditions and validators: Previous status Condition Separation of Duties Condition Hide transition from user Condition Field has been modified Validator Field required Validator, which also includes comments Field has single value Validator Previous state Validator Parent status Validator

            Hi Mark,

            If we focus on JQL, for my usage, Subqueries (on any field) are essential.

            Here's a quick example of what I'm trying to achieve : I want to list every User Stories in a project with duplicated Subtasks.

            Naturally I would think of something like :

            project='KEY' AND issueType='Story' AND hasSubtasks(hasLinks='is duplicated' OR hasLinks='duplicates')
            

            With JQL Search Extension, I can do research on things like number of comments / subtasks etc. which is already a big plus when you compare to the standard Cloud JQL.

            Sylvain MERLIN added a comment - Hi Mark, If we focus on JQL, for my usage, Subqueries (on any field) are essential. Here's a quick example of what I'm trying to achieve : I want to list every User Stories in a project with duplicated Subtasks. Naturally I would think of something like : project= 'KEY' AND issueType= 'Story' AND hasSubtasks(hasLinks= 'is duplicated' OR hasLinks= 'duplicates' ) With JQL Search Extension, I can do research on things like number of comments / subtasks etc. which is already a big plus when you compare to the standard Cloud JQL.

            Many thanks to Sylvain and Aaron for the feedback.

            We do not currently have good solution for Workflow Conditions nor Validations.

            Adaptavist are actively working on JQL functions right now and whilst we won't have full server feature parity we are making decent progress. Our recent spike has resulted in a way to achieve queries like:

            • numberOfLinks > 0
            • numberOfSubtasks > 0
            • hasLinks = "is duplicated by"

            You may have already tried the Cloud and noticed it did not include Script Fields but you can achieve a "Calculated Field" as part of a workflow Post Function (as a starter).

            Script Listeners is already included.

            Services is still possible and we plan to spike on that in the coming months.

            Sylvain: I'm interested in where JQL Search Extensions for JIRA falls short (to be sure we don't do the same)?

            regards, Mark.

            Mark McCormack (Adaptavist) added a comment - Many thanks to Sylvain and Aaron for the feedback. We do not currently have good solution for Workflow Conditions nor Validations. Adaptavist are actively working on JQL functions right now and whilst we won't have full server feature parity we are making decent progress. Our recent spike has resulted in a way to achieve queries like: numberOfLinks > 0 numberOfSubtasks > 0 hasLinks = "is duplicated by" You may have already tried the Cloud and noticed it did not include Script Fields but you can achieve a "Calculated Field" as part of a workflow Post Function (as a starter). Script Listeners is already included. Services is still possible and we plan to spike on that in the coming months. Sylvain: I'm interested in where JQL Search Extensions for JIRA falls short (to be sure we don't do the same)? regards, Mark.

            Aaron Sua added a comment -

            @mmccormack
            Features I consider essential for this plugin:
            Workflow Conditions
            Workflow Validations
            JQL Functions
            Scripted Fields

            Features I consider nice to have:
            Behaviours
            Script Listeners
            Services

            Aaron Sua added a comment - @mmccormack Features I consider essential for this plugin: Workflow Conditions Workflow Validations JQL Functions Scripted Fields Features I consider nice to have: Behaviours Script Listeners Services

            I agree with Aaron, the cloud version is very limited ; I need to find parent issues by searching in their subtasks' fields with JQL : No way to do it now.

            Another version of ScriptRunner allowed to use issueFunction to do this : https://jamieechlin.atlassian.net/wiki/pages/viewpage.action?pageId=57999378#ScriptedJQLFunctions-parentsOf(Subquery)

            Too bad it does not work with On Demand.

            This plugin looked like a solution JQL Search Extensions for JIRA but still not enough.

            Sylvain MERLIN added a comment - I agree with Aaron, the cloud version is very limited ; I need to find parent issues by searching in their subtasks' fields with JQL : No way to do it now . Another version of ScriptRunner allowed to use issueFunction to do this : https://jamieechlin.atlassian.net/wiki/pages/viewpage.action?pageId=57999378#ScriptedJQLFunctions-parentsOf(Subquery ) Too bad it does not work with On Demand. This plugin looked like a solution JQL Search Extensions for JIRA but still not enough.

            Hi Aaron, I didn't see your name on our list of ScriptRunner for JIRA Cloud evaluators nor those that uninstalled which is a shame. I'd love to understand which features were missing so Adaptavist can have the chance to respond to those that are (and aren't) possible. Perhaps we've already done that and I've missed it.

            Please feel free to raise an issue on our support portal if you have the time to discuss it further.

            regards, Mark.

            Mark McCormack (Adaptavist) added a comment - Hi Aaron, I didn't see your name on our list of ScriptRunner for JIRA Cloud evaluators nor those that uninstalled which is a shame. I'd love to understand which features were missing so Adaptavist can have the chance to respond to those that are (and aren't) possible. Perhaps we've already done that and I've missed it. Please feel free to raise an issue on our support portal if you have the time to discuss it further. regards, Mark.

              Unassigned Unassigned
              hlechner HenriqueA
              Votes:
              111 Vote for this issue
              Watchers:
              129 Start watching this issue

                Created:
                Updated:
                Resolved: