Releases: lopperman/jira-issue-analysis
Releases · lopperman/jira-issue-analysis
0.6.4-beta
🦙 🦙
JiraTIS-0.6.4-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.6.3-beta...0.6.4-beta
Full Changelog: 0.6.2-beta...0.6.3-beta
Full Changelog: 0.6.1-beta...0.6.2-beta
Highlights for v0.6.4
Issue Analysis now contains summary charts to compare single issue against averages of all other issue queried (v0.6.4-beta)
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
 |
 |
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
 |
 |
| First Run screen 3 | First Run screen 4 |
|---|---|
 |
 |
| Issue Summary | Issue ChangeLog |
|---|---|
 |
 |
| Multiple Jira Configs | empty |
|---|---|
 |
empty |
0.6.3-beta
🦙 🦙
JiraTIS-0.6.3-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.6.2-beta...0.6.3-beta
Full Changelog: 0.6.1-beta...0.6.2-beta
Full Changelog: 0.6.0-beta...0.6.1-beta
Highlights
Added status and blocker breakdown charts to Issue Summary (v0.6.3-beta)
**Added Options (Config Menu--> Edit Config Options), including option to automatically record and save (single html file) output from various issue analytics/reports ** (v0.6.2)
Various formatting improvements (v0.6.2)
Added dynamic Cycle-Time Analysis: (v0.6.1)
- Main Menu -- > Issue Summary Visualization -- > Build Cycle Time
- Select a Jira Issue Type (e.g. Story)
- Select Status for starting Cycle Time Measurement
- Select Status for ending Cycle Time Measurement
- Enter Start Date to filter issues that entered 'End' Issue State
- Enter End Date to filter issues that entered 'End' Issue State
Issue will be analyzed and overall and weekly summaries will display. Screenshot below shows Weekly Rendered data:
Highlights for v0.5.8
- Modified Issue Status to exclude weekends from blocked time calculations
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
JiraTIS-0.6.2-beta
🦙 🦙
JiraTIS-0.6.2-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.6.1-beta...0.6.2-beta
Full Changelog: 0.6.0-beta...0.6.1-beta
Full Changelog: 0.5.9-beta...0.6.0-beta
Highlights
**Added Options (Config Menu--> Edit Config Options), including option to automatically record and save (single html file) output from various issue analytics/reports ** (v0.6.2)
Various formatting improvements (v0.6.2)
Added dynamic Cycle-Time Analysis: (v0.6.1)
- Main Menu -- > Issue Summary Visualization -- > Build Cycle Time
- Select a Jira Issue Type (e.g. Story)
- Select Status for starting Cycle Time Measurement
- Select Status for ending Cycle Time Measurement
- Enter Start Date to filter issues that entered 'End' Issue State
- Enter End Date to filter issues that entered 'End' Issue State
Issue will be analyzed and overall and weekly summaries will display. Screenshot below shows Weekly Rendered data:
Highlights for v0.5.8
- Modified Issue Status to exclude weekends from blocked time calculations
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
Jira-TIS-0.6.1-beta
🦙 🦙
JiraTIS-0.6.1-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.6.0-beta...0.6.1-beta
Full Changelog: 0.5.9-beta...0.6.0-beta
Highlights for v0.6.1
Added dynamic Cycle-Time Analysis:
- Main Menu -- > Issue Summary Visualization -- > Build Cycle Time
- Select a Jira Issue Type (e.g. Story)
- Select Status for starting Cycle Time Measurement
- Select Status for ending Cycle Time Measurement
- Enter Start Date to filter issues that entered 'End' Issue State
- Enter End Date to filter issues that entered 'End' Issue State
Issue will be analyzed and overall and weekly summaries will display. Screenshot below shows Weekly Rendered data:
Highlights for v0.5.8
- Modified Issue Status to exclude weekends from blocked time calculations
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
JiraTIS-0.6.0-beta
🦙 🦙
JiraTIS-0.6.0-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.5.9-beta...0.6.0-beta
Full Changelog: 0.5.8-beta...0.5.9-beta
Full Changelog: 0.5.7-beta...0.5.8-beta
Highlights for v0.5.8
- Modified Issue Status to exclude weekends from blocked time calculations
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
JiraTIS-0.5.9-beta
🦙 🦙
JiraTIS-0.5.9-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.5.8-beta...0.5.9-beta
Full Changelog: 0.5.7-beta...0.5.8-beta
Full Changelog: 0.5.6-beta...0.5.7-beta
Highlights for v0.5.8
- Modified Issue Status to exclude weekends from blocked time calculations
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
JiraTIS-0.5.8-beta
🦙 🦙
JiraTIS-0.5.8-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.5.7-beta...0.5.8-beta
Full Changelog: 0.5.6-beta...0.5.7-beta
Highlights for v0.5.8
- Modified Issue Status to exclude weekends from blocked time calculations
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
JiraTIS-0.5.7-beta
🦙 🦙
JiraTIS-0.5.7-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.5.6-beta...0.5.7-beta
Full Changelog: 0.5.5-beta...0.5.6-beta
Highlights for v0.5.7
- Added ability to filter change log history by selecting from list of change log item fields. Video
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
0.5.6-beta
🦙 🦙
JiraTIS-0.5.6-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.5.5-beta...0.5.6-beta
Full Changelog: 0.5.4-beta...0.5.5-beta
Highlights for v0.5.6
- Caching enabled for search results. If you want to look at change logs, view Issue Summaries, and see breakdown of blockers for the same list of issues, Jira will only be queried 1 time!
- Combined 1) Selecting saved JQL snippet, 2) manually entering JQL, 3) entering a list of issues -- all into a single interaction with the app
- Created ability to move backwards and forward or to go to a specific index in list of issues (for Change Log area)
Additional screen shots for this release can be viewed here
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |
JiraTIS-0.5.5-beta
🦙 🦙
JiraTIS-0.5.5-beta
TIME IN STATUS ANALYSIS OF JIRA ISSUES
Full Changelog: 0.5.4-beta...0.5.5-beta
Full Changelog: 0.5.3-beta...0.5.4-beta
Full Changelog: 0.5.2-beta...0.5.3-beta
This version utilizes asynchronous issue and changelog retrieval for viewing ChangeLog information, and the Analyze Issues area. It's very fast!
GENERAL NOTES (Click to Expand)
- VIEW AND MANAGE CUSTOM ISSUES STATUS CATEGORIES
-
- MANAGED IN A LOCAL CONFIG FILE, CUSTOMIZE ANY STATUS TO BE SEEN AS 'TO DO', 'ACTIVE', 'DONE', OR 'IGNORE'
- FOR ANY ISSUE YOU CAN SEE AN INSTANT SNAPSHOT WHICH INCLUDES:
-
- FIRST DATE ISSUE BECAME ACTIVE (FIRST STATUS CATEGORIES AS 'ACTIVE WORK'
-
- EARLIEST DATE ISSUE ENTERED ANY STATUS
-
- LATEST DATE ISSUE LEFT ANY STATUS
-
- NUMBER OF TIMES ISSUE ENTERED A STATUS
-
- TOTAL CALENDAR AND BUSINESS DAYS ISSUE REMAINED IN ANY STATUS
-
- 'ACTIVE' TIME AUTOMATICALLY ADJUSTED TO 'PASSIVE' TIME FOR ANY ACTIVE TIME SPANS THAT OVERLAP WITH BLOCKED STATUS.
-
- FULL CHANGE LOG DETAILS CAN BE VIEWED, DOWNLOADED AS CSV OR EXPORTED AS HTML
-
- ADDITIONAL SUMMARIZATION AND FILTERING IN DEVELOPMENT
INSTALLATION AND GETTING STARTED
DEPENDENCIES
- .Net Core 7 Framework Download
- For Macs with Intel Chip, download x64 version, for M1/M2 chips, download Arm64 version)
MAC USERS
- For Mac users, after you have installed the .Net Core Framework, open Terminal and type the following command to create a shortcut to the DotNet.exe. You may need to use sudo in front of the command:
ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/
WINDOWS USERS
- Use Windows Terminal (wt.exe) for the best experience with icons and colors. Free download from microsoft
- If you're using Windows Terminal (WT.exe) or Windows Powershell, the following will enable emojis and unicode support, which includes increasing the colors that can be used from 16 to 256:
[console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()- Include the above in your profile.ps1 file and unicode and emoji support will always be available. This link provides step-by-step instruction for create a new Powershell 'profile.ps1' file, if needed.
- To enable Unicode support in Windows for cmd.exe, do the following:
- Press the Windows key, then press 'R'
- Type:
Run intl.cpl - Click the Administrative tab
- Click the Change system locale button
- Check the "Beta/Use Unicode UTF-8 for worldwide language support" checkbox.
- Reboot
OBTAINING JIRA API KEY
- If you do not have an API key for your Atlassian account, instructions can be found here for generating one
FIRST TIME RUNNING APP
- To use, download and unzip publish.zip (found at the end of these release notes)
- From a command prompt, navigate to unzipped directory and type:
dotnet JiraStates.dll;(The JiraStates.dll should be in the folder where the command in executed)
SCREENSHOTS
- 0.4.4 includes some general visualization summaries
| Visual Status | Visual Blockers |
|---|---|
|
|
ADDITIONAL SCREENSHOTS (Click to Expand)
0.4.0-alpha includes improved 'first run' experience, which enables creation of new json configuration file
| First Run screen 1 | First Run screen 2 |
|---|---|
|
|
| First Run screen 3 | First Run screen 4 |
|---|---|
|
|
| Issue Summary | Issue ChangeLog |
|---|---|
|
|
| Multiple Jira Configs | empty |
|---|---|
|
empty |