jira_report 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +7 -2
- data/lib/jira_report/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: e4f3e56f1a9b4f7effe382bde1d173ab632a4dd9
|
|
4
|
+
data.tar.gz: d8afe2ed1eaf44854bcb5dcd78f6c975afb58dfc
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 92c226bfa8364188a8439b104cdc20e1dac3d45ffa066729c5d759ef54841c001be35aad023ea351a4244c387d0860a94a5eb2353504681dfb2cfaf13b36ee19
|
|
7
|
+
data.tar.gz: adf1fb6273f165ee741471bcd0e5f58a3e4323fb0defb88ede9c283e1bf6eac07ce8614c83d5d2035bbbc61996717bfb53579ff6bc8f7b348f0fbb69f172abc1
|
data/README.md
CHANGED
|
@@ -1,5 +1,4 @@
|
|
|
1
|
-
Jira Report [](https://rubygems.org/gems/jira_report) [](https://travis-ci.org/veelenga/jira_report)
|
|
2
|
-
===========================
|
|
1
|
+
#Jira Report [](https://rubygems.org/gems/jira_report) [](https://travis-ci.org/veelenga/jira_report)
|
|
3
2
|
|
|
4
3
|
Queries user activities from jira for specified period of time and prints it to console.
|
|
5
4
|
|
|
@@ -11,6 +10,7 @@ $ gem install jira_report
|
|
|
11
10
|
##Usage
|
|
12
11
|
|
|
13
12
|
Just run it. `jira-report` will ask you your jira location, who you are and what's your password:
|
|
13
|
+
|
|
14
14
|
```
|
|
15
15
|
$ jira-report
|
|
16
16
|
Jira url: jira.company.com
|
|
@@ -47,6 +47,7 @@ Closed: 5
|
|
|
47
47
|
`url`, `username`, `password` and some other parameters can be added to [configuration file](#configuration). Also you can use mixed approach (keep some options in file, others enter from command line). For example if you do not want to keep password in configuration file, just don't, you will be asked.
|
|
48
48
|
|
|
49
49
|
Also you can use it directly in ruby:
|
|
50
|
+
|
|
50
51
|
```ruby
|
|
51
52
|
require 'jira_report'
|
|
52
53
|
|
|
@@ -74,18 +75,22 @@ print_issues(weekly_closed)
|
|
|
74
75
|
Path to configuration file can be specified by `-c` command line argument. `~/.jira-report` is default.
|
|
75
76
|
|
|
76
77
|
There are three main options in config file to query jira:
|
|
78
|
+
|
|
77
79
|
```
|
|
78
80
|
url=jira.company.com
|
|
79
81
|
username=username
|
|
80
82
|
password=s3cr3t
|
|
81
83
|
```
|
|
84
|
+
|
|
82
85
|
all those are optional and if not specified user will be asked to enter it from command line.
|
|
83
86
|
|
|
84
87
|
Period is set by two options `period_from` and `period_till`. Both options support [advanced jira searching](https://confluence.atlassian.com/display/JIRA/Advanced+Searching) and accept dates, jira functions, aliasing. For example:
|
|
88
|
+
|
|
85
89
|
```
|
|
86
90
|
period_from=-1w
|
|
87
91
|
period_till=now()
|
|
88
92
|
```
|
|
93
|
+
|
|
89
94
|
If those options not specified in configuration file, last week activities will be queried (just as in example above).
|
|
90
95
|
|
|
91
96
|
You can look at configuration file [sample](example/jira-report.sample) in repository.
|
data/lib/jira_report/version.rb
CHANGED