Comments (10)
Hi @cygnus2048 - Sorry for the inconvenience and until the new version is working as expected, old version would continue to be there and I would not remove it.
However, did you try to reproduce this issue with Web version of Jira Assistant? I believe this issue has already been resolved in Web Version. Please verify this with Web version once and let me know if it resolves your issue. If I get the confirmation that it is resolved in Web version, then I will publish the updates for extension.
I would give sufficient time to understand everyone is comfortable using the new version and then first hide the old version to see if anyone is impacted and then only will remove the old one. It would take lot more months before I remove the old one.
To answer the question why New one is required:
I understand it was not working for you, but it is temporary and this is the only open issue reported so far with New report. There would be always edge case scenario and it would get better in time. And if you look at the settings of new report, it is supporting lot more scenarios / configurations and allows you to configure it to the deepest of your needs.
Additionally this is duplicate of #253 & #254 and hence I would be closing this issue after waiting for couple of more days to get your reply.
from jira-assistant.
Hi @cygnus2048 - I am closing this issue considering this issue is duplicate and is resolved. Please retest this issue with Jira Assistant v2.48 or with Web version and let me know if you still face any issue.
from jira-assistant.
I have verified with v2.48 and it does show correctly now. I would like to point out though that I find the appearance of the "new" much less desirable than the "old" so I will continue to use the "old" and I ask that you do not remove it and please leave it an option for those of us who prefer it. Thank you.
from jira-assistant.
Hi @cygnus2048, when you say "new" report is much less desirable than "old", what do you mean by it? Why do you prefer to use "old" report when there are lot more features added than old and what ever is available in "old" is still available in "new" report as well.
If you talking about look and feel, please look at the settings of "new" report and you can change the configuration to use same styling as that of "old" report.
I would like to let you know that there will not be any more enhancement in Old report as it is migrated from different technology earlier and hard to maintain or do customizations. That was the first reason to take time in building a new report instead of adding feature to existing one.
from jira-assistant.
Yes, I do mean the look and feel. The colored background is much easier to glance at for info compared to the new bars at the bottom. Moreover, when expanding on a user, the new view splits each item in multiple lines, which spreads out the hours on the right hand side to double the vertical space it used to use. Also, not only is splitting the ticket name into multiple lines (putting the hour details on line two) it is truncating the task name as well as not showing the state. Just many things about this new which I don't care for at all.
from jira-assistant.
Thank you @cygnus2048 for your response. Here are my comments for your issues:
The colored background is much easier to glance at for info compared to the new bars at the bottom.
A) Background color is not gone, you can still change it from configurations as I mentioned earlier. Open configurations and go to Formatting tab, expand more options and you will see the following settings which lets you get the old background highlighting back:
Moreover, when expanding on a user, the new view splits each item in multiple lines, which spreads out the hours on the right hand side to double the vertical space it used to use.
A) This is not true. In fact, New report is more compact and uses less vertical space. May be you are using different log hour format for both the report. Change the log hour format configuration from Report configurations, Formatting tab and you should see new report consume lesser space than old report.
New report (Looks better and more compact for same set of data):
Old report (Uses lot more space)
Also, not only is splitting the ticket name into multiple lines
A) What do you mean by splitting the ticket name. What do you refer as ticket name? What ever it is, I don't think anything is splitted to multiple lines
(putting the hour details on line two)
A) As mentioned above, you may be using different hour format in both the reports. If you use same formatting, New report would still look more compact.
it is truncating the task name as well
A) Are you referring to "issue summary" by any chance? I hope issue summary are just an indicator to understand what issue users had logged work on. I don't really see any need to display display the whole summary and span the report to double in height. And this is not my individual decision, but based on lots of feedback received from users over years.
Any way, if you want to look at whole summary for some cases, just hovering over the summary displays the complete text as tooltip. Any way, if you feel it is necessary, let this not be a problem, I will add an additional settings in upcoming release to show whole summary like in old report.
not showing the state
This is already a setting for you to configure. Just enable "Show status" checkbox from Fields list tab under Report Configurations and you should see it.
Almost all these changes are not just based on my preference and is based on user feedback and minimal UX consultations as well. And none of the features are lost in new report. Everything is behind configuration only and you can customize it the way you need it.
from jira-assistant.
I appreciate the detailed response. I was able to configure the background colors, so thank you for that.
Regarding the truncation and multiple lines. It is hard to describe so I will try to show the difference...
Notice a nice single line in the old, but the new is truncated as well as the hours put on the second line even though there is a bunch of available space left.
from jira-assistant.
Ok @cygnus2048 I get it now. Thank you for the screenshot. Will fix this as well in upcoming release. And if there are any other issues / suggestions, please feel free to let me know and I will address it ASAP.
And as I told earlier, until all the issues are resolved and everyone is comfortable using the new report, old report would remain. So you need not worry about old report getting removed.
from jira-assistant.
I found one other minor annoyance with the new report. When I click on refresh it collapses all the users I had expanded. The old report maintains this and does not collapse them.
from jira-assistant.
Hi @cygnus2048 - Both the issues you mentioned above is resolved and is already available in Web version of Jira Assistant. This would be published to extension as part of JA v2.49 in next couple of weeks max. Until then if you would like to try it to see if it works as expected, you can try it out in Web version by accessing https://app.jiraassistant.com
from jira-assistant.
Related Issues (20)
- Add custom fields to work log report HOT 7
- JA gets stuck while logging in with "Authorizing", "Setting Up", or "Loading" HOT 15
- Text not readable in Dark theme HOT 1
- Time Tracker not showing up HOT 4
- JQL for worklogs fails with large project HOT 4
- Worklog: Column headings become 'detached' when scrolling and expanding user information HOT 2
- Customize "Done" statuses for Sprint Report
- Sprint Report - Worklog detail page: "Exclude hours logged out of sprint" does not work
- Cloud App version installation loop. HOT 9
- When adding users under user groups, it throws error saying that "One or more of the actions failed .Look at the console for more details" HOT 2
- Unable to connect/login to JIRA Assistant HOT 2
- New Worklog Report doesn't auto Refresh on adding new Worklog time (both extension & web) HOT 3
- Request to add the feature where we can generate 1 worklog report from 2 different Jira's HOT 1
- Worklog Calendar fails to load from Jira Cloud HOT 1
- View Worklog Calendar for Teammembers
- Worklog report - automation HOT 2
- Share the Worklog Report HOT 2
- CORS Preflight did not succeed on custom Jira server HOT 1
- Mark issues as favorite and use it later from a list at new worklog
- Error: "com.atlassian.jira.issue.search.vsearch.SearchInternalException: Failed to run query" when running Worklog Report HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jira-assistant.