Skip to content

Instantly share code, notes, and snippets.

@christiangalsterer
Last active June 4, 2020 21:46
Show Gist options
  • Star 6 You must be signed in to star a gist
  • Fork 3 You must be signed in to fork a gist
  • Save christiangalsterer/1b24f2b42aa39ba63a92 to your computer and use it in GitHub Desktop.
Save christiangalsterer/1b24f2b42aa39ba63a92 to your computer and use it in GitHub Desktop.
Dashing Number of issues in Jira query

Description

A Dashing widget to display the number of issues returned by a Jira filter search. The number of issues will be displayed using the Numbers widget. See also the Atlassian Jira: Number of issues in a Jira filter query for a more generalised version which allows to run any JQL query directly from the widget.

Dependencies

The following dependencies are required. Please add them to your dashing gemfile.

gem 'jira-ruby', :require => 'jira'

Run bundle install

Installation

If you want to install the widget manually put the file jira_number_of_issues_in_filter.rb file into the /jobs directory.

If you want to install the widget automatically type:

dashing gist 1b24f2b42aa39ba63a92

Usage

1. Adjust Job Configuration

Change the JIRA_PROPS in the jira_number_of_issues_in_filter.rb file to the correct URL of your Jira installation, e.g.

JIRA_PROPS = {
  'url' => URI.parse("https://localhost:8080"),
  'username' => 'username',
  'password' => 'password',
  'proxy_address' => nil,
  'proxy_port' => nil
}

Put all the filter names or filter ids in the filter_mapping, e.g.:

filter_mapping = {
  'filter1' => { :filter => '3' },
  'filter2' => { :filter => 'My Open Items' }
}

2. Adjust Dashboard Configuration

Add the following widget HTML snippet for each jql filter to your dashboard erb file.

<li data-row="1" data-col="2" data-sizex="1" data-sizey="1">
  <div data-id="filter1" data-view="Number" data-title="My Open Items"></div>
</li>

Multiple widgets can be shown on a dashboard by repeating the above snippet and changing data-id along with the filter name specified in the filter_mapping in the jobs/jira_number_of_issues_in_filter.rb file.

Preview

Compatibility

The widget was tested with the following Jira versions.

Jira Tested By Verified
5.0.6 Christian Galsterer OK
6.1.7 Christian Galsterer OK

License

The widget is provided unter the Apache License, Version 2.0. You may obtain a copy of the License at (http://www.apache.org/licenses/LICENSE-2.0)

require 'jira'
JIRA_PROPS = {
'url' => URI.parse("https://localhost:8080"),
'username' => 'username',
'password' => 'password',
'proxy_address' => nil,
'proxy_port' => nil
}
# the key of this mapping must be a unique identifier for your jql filter, the according value must be the jql filter id or filter name that is used in Jira
filter_mapping = {
'filter1' => { :filter => '0' },
}
jira_options = {
:username => JIRA_PROPS['username'],
:password => JIRA_PROPS['password'],
:context_path => JIRA_PROPS['url'].path,
:site => JIRA_PROPS['url'].scheme + "://" + JIRA_PROPS['url'].host,
:auth_type => :basic,
:ssl_verify_mode => OpenSSL::SSL::VERIFY_NONE,
:use_ssl => JIRA_PROPS['url'].scheme == 'https' ? true : false,
:proxy_address => JIRA_PROPS['proxy_address'],
:proxy_port => JIRA_PROPS['proxy_port']
}
last_issues = Hash.new(0)
filter_mapping.each do |filter_data_id, filter|
SCHEDULER.every '10s', :first_in => 0 do |job|
last_number_issues = last_issues['filter_data_id']
client = JIRA::Client.new(jira_options)
current_number_issues = client.Issue.jql("filter in (\"#{filter[:filter]}\")").size
last_issues['filter_data_id'] = current_number_issues
send_event(filter_data_id, { current: current_number_issues, last: last_number_issues})
end
end
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2014 Christian Galsterer
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
@diverser
Copy link

diverser commented Jul 7, 2014

Always show 50 count. But it over 50. I think, the count of jql limit in rest api or something in jira-ruby module

@amitjethani
Copy link

I have the same problem as diverser – for any query with over 50 results, the widget shows 50.

@hemnam01
Copy link

hemnam01 commented Aug 1, 2014

By default Jira api return max 50 result, in above code for jira_options if you pass value :max_results = 1000
you will get 1000 issues.

jira_options = {
:username => JIRA_PROPS['username'],
:password => JIRA_PROPS['password'],
:context_path => JIRA_PROPS['url'].path,
:site => JIRA_PROPS['url'].scheme + "://" + JIRA_PROPS['url'].host,
:auth_type => :basic,
:ssl_verify_mode => OpenSSL::SSL::VERIFY_NONE,
:use_ssl => JIRA_PROPS['url'].scheme == 'https' ? true : false,
:proxy_address => JIRA_PROPS['proxy_address'],
:proxy_port => JIRA_PROPS['proxy_port']
:max_results=1000
}

Hope this will help

@derwin12
Copy link

derwin12 commented Aug 6, 2014

:max_results => 1000 did not work for me.

Documentation makes no mention of this option existing
http://rubydoc.info/gems/jira-ruby/0.1.11/frames

You have to be sure to get the right gem installed.

https://github.com/sumoheavy/jira-ruby

gem 'jira-ruby', :git => 'git://github.com/sumoheavy/jira-ruby.git'

For my config I found it easier to simply edit the gem jira/resource/issue.rb and add one line..

url += "&maxResults=500"     << Add this line
response = client.get(url)

@andrewsmhay
Copy link

dashing install 1b24f2b42aa39ba63a92

not

dashing gist 1b24f2b42aa39ba63a92

@gsachane
Copy link

gsachane commented Jun 4, 2015

I have few JIRA filters which I am mapping to get the results to display in my widgets.

e.g. filter1, filter2 etc

One of the filter(filter3) is showing 200 issues. I need to hardcode 20 more issues to that filter(filter3) which are coming from another source. This number(20) will never change. Can I do that in filter mapping?

@Ishino
Copy link

Ishino commented Jun 25, 2015

I added the following:

query_options = {
  :fields => [],
  :start_at => 0,
  :max_results => 1000
}
current_number_issues = client.Issue.jql("filter in (\"#{filter[:filter]}\")", query_options).size

And this allowed me to get all issues instead of just 50. I hope it helps.

http://stackoverflow.com/questions/25135622/jira-ruby-gem-limiting-number-of-returned-isues

Copy link

ghost commented Aug 18, 2015

Surely the send event should be this:

send_event(filter_data_id, { current: current_number_issues, last: last_issues['filter_data_id']})

Otherwise you just get the same last_issues count sent for every event regardless of the filter?

@ulich
Copy link

ulich commented Nov 11, 2015

The change rate is wrong when you have more than one filter configured. The problem is this:

last_number_issues = last_issues['filter_data_id']
...
last_issues['filter_data_id'] = current_number_issues

which should rather be

last_number_issues = last_issues[filter_data_id]
...
last_issues[filter_data_id] = current_number_issues

(note that filter_data_id is no string, instead it is the value of the variable)

@emoleumassi
Copy link

emoleumassi commented Nov 16, 2016

i have some issues:

first issue:

/Users/users/.rvm/gems/ruby-2.2.4/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require': cannot load such file -- jira (LoadError)`

with thoses settings:

Gemfile:

source 'https://rubygems.org'

gem 'dashing'

## Remove this if you don't need a twitter widget.
gem 'twitter', '>= 5.9.0'

gem 'teamcity-ruby-client'
gem 'httparty'

gem 'jira-ruby' :require => 'jira'

the jira_number_of_issues_in_filter.rb:

require 'jira'

JIRA_PROPS = {
  'url' => URI.parse("https://SSSSS"),
  'username' => 'user',
  'password' => 'passwd,
  'proxy_address' => nil,
  'proxy_port' => nil
}

# the key of this mapping must be a unique identifier for your jql filter, the according value must be the jql filter id or filter name that is used in Jira
filter_mapping = {
  'filter1' => { :filter => 'aaaa' }
}

when i modifie the GEmfile to gem 'jira-ruby', with require require 'jira-ruby' in ruby file i get another problem:

JIRA::HTTPError
/Users/users/.rvm/gems/ruby-2.2.4/gems/jira-ruby-1.1.3/lib/jira/request_client.rb:16:in `request'
/Users/users/.rvm/gems/ruby-2.2.4/gems/jira-ruby-1.1.3/lib/jira/client.rb:213:in `request'
/Users/users/.rvm/gems/ruby-2.2.4/gems/jira-ruby-1.1.3/lib/jira/client.rb:191:in `get'
/Users/users/.rvm/gems/ruby-2.2.4/gems/jira-ruby-1.1.3/lib/jira/resource/issue.rb:64:in `jql'
/Users/users/.rvm/gems/ruby-2.2.4/gems/jira-ruby-1.1.3/lib/jira/base_factory.rb:33:in `block (2 levels) in delegate_to_target_class'
/Users/users/../../jobs/jira_number_of_issues_in_filter.rb:35:in `block (2 levels) in <top (required)>'
/Users/users/.rvm/gems/ruby-2.2.4/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in `call'
/Users/users/.rvm/gems/ruby-2.2.4/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in `trigger_block'
/Users/users/.rvm/gems/ruby-2.2.4/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in `block in trigger'
/Users/users/.rvm/gems/ruby-2.2.4/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in `call'
/Users/users/.rvm/gems/ruby-2.2.4/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in `block in trigger_job'


Copy link

ghost commented Dec 4, 2016

Hi, got the same message as @emoleumassi

@zisternov
Copy link

Hey @emoleumassi, @rlvdijk! Have you guys figured out what's going on with `/Users/users/.rvm/gems/ruby-2.2.4/gems/backports-3.6.8/lib/backports/std_lib.rb:9:inrequire': cannot load such file -- jira (LoadError)``?

Spent tons of times last night to figure out the cause of it and found no solution.

Would love any suggestions as for how to display Jira count in my Dashing dashboard.

Thanks in advance!

@Feuer-sturm
Copy link

@zisternov:
Please check your files to use require 'jira-ruby' instead of require 'jira'

My Gemfile looks like this:

require 'jira-ruby'

gem 'smashing'
gem 'jira-ruby' 

@poalcospe
Copy link

Does anyone knows if it's possible to change background color function of percentage increasing or decreasing ? Since there is no scss file, I'm not sure if it's possible...

@motherboard1999
Copy link

motherboard1999 commented Apr 5, 2018

With this job file, the widget can change the color and it shows more than 50:

require 'jira-ruby'

JIRA_PROPS = {
  'url' => URI.parse("https://"),
  'username' => '',
  'password' => '',
  'proxy_address' => nil,
  'proxy_port' => nil
}

query_mapping = {
  'query1' => {
      :query => 'filter1',
      :change_color => true,
   },
  'query2' => {
      :query => 'filter2',
      :change_color => false,
   },
  'query3' => {
      :query => 'filter3',
      :change_color => false,
   },
}

jira_options = {
  :username => JIRA_PROPS['username'],
  :password => JIRA_PROPS['password'],
  :context_path => JIRA_PROPS['url'].path,
  :site => JIRA_PROPS['url'].scheme + "://" + JIRA_PROPS['url'].host,
  :auth_type => :basic,
  :ssl_verify_mode => OpenSSL::SSL::VERIFY_NONE,
  :use_ssl => JIRA_PROPS['url'].scheme == 'https' ? true : false,
  :proxy_address => JIRA_PROPS['proxy_address'],
  :proxy_port => JIRA_PROPS['proxy_port']
}

last_issues = Hash.new(0)

query_mapping.each do |query_data_id, query|
  SCHEDULER.every '9s', :first_in => 0 do |job|
    last_number_issues = last_issues[query_data_id]
    client = JIRA::Client.new(jira_options)
    # max_results: 0 will return only the count of issues matching the query
    current_number_issues = client.Issue.jql(query[:query], { max_results: 0 })
    last_issues[query_data_id] = current_number_issues

    if query[:change_color] and last_issues[query_data_id] > 0
      status = 'warning'
    else
      status = 'ok'
    end

    send_event(query_data_id, { current: current_number_issues, last: last_number_issues, status: status})

  end
end

@rompic
Copy link

rompic commented Nov 5, 2019

if you only want the number of issues use max_results: 0 as also stated in @motherboard1999's example.
more information here:
https://github.com/sumoheavy/jira-ruby/pull/167/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment