[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-08-02 Thread Filip Maj (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111437#comment-16111437
 ] 

Filip Maj commented on CB-12670:


I believe we will be discussing the impending move over to GitHub on the dev 
mailing list soon-ish - feel free to chime in there. We will be discussing on 
the dev mailing list things like if / how to move over existing issues from 
JIRA to GitHub, or whether we declare JIRA issue bankruptcy, etc.

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-08-02 Thread Jan Piotrowski (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111406#comment-16111406
 ] 

Jan Piotrowski commented on CB-12670:
-

<3 <3 <3 Awesome news.

Let me know if I can support this in any way.

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-08-02 Thread Filip Maj (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111332#comment-16111332
 ] 

Filip Maj commented on CB-12670:


Update: Apache Infra has set up cordova-browser 
(http://github.com/apache/cordova-browser) as a standalone GitHub-based repo 
for us a test! We haven't asked to enable issues on there yet, but that is 
coming. So: JIRA will be gone at some point in the near-ish future.

As for issues.cordova.io, with GitHub taking over soon, I'm not sure that link 
will be relevant anymore.

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-08-02 Thread Jan Piotrowski (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1666#comment-1666
 ] 

Jan Piotrowski commented on CB-12670:
-

That's great.

issues.cordova.io not actually redirecting to the "issues" view of JIRA is the 
worst problem right now. People have to fight their way through JIRA after you 
give them the issues.cordova.io link.

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-07-14 Thread Filip Maj (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088174#comment-16088174
 ] 

Filip Maj commented on CB-12670:


I've tried to make some changes to the boards to make some of this stuff 
clearer.

In particular there are a series of '*-next' boards per component now. The idea 
is to use these leading up to a release for a particular component to allow you 
to see what's left to do, what's in progress and what's done. Issues labeled 
with e.g. "android-next" will show up under the "android-next" board.

Also added a wider-view 'backlog' board (similarly tagged via the backlog 
label) that shows _all_ components: 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=195

Agree we should be more diligent with adding proper Releases per component. I 
will try to include that in my workflow.

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-06-13 Thread Jan Piotrowski (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047771#comment-16047771
 ] 

Jan Piotrowski commented on CB-12670:
-

With the new JIRA update that was activated yesterday (?) the start page of the 
Cordova JIRA now is a (pretty useless) Kanban board. The URL behind 
"issues.cordova.io" should probably be updated to something more useful like 
https://issues.apache.org/jira/projects/CB/issues

Another thing I noticed is that the search field in the top right default to 
searching all Apache projects instead of just the one you are in - Cordova :/

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-04-20 Thread Jan Piotrowski (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976978#comment-15976978
 ] 

Jan Piotrowski commented on CB-12670:
-

Thanks for the response.

>  I'd much prefer GitHub issues. We'd have more control and, I think, more 
> engagement. But thus far that has proved elusive, and so we can only do with 
> what we have.

Is there any way we can work towards change here?
Anywhere to +1, send an email, etc? 
Any blockers that can be worked on so a migration could become feasable?

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-04-20 Thread Kerri Shotts (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976962#comment-15976962
 ] 

Kerri Shotts commented on CB-12670:
---

So, a few things:

# Wow; those timings are atrocious. Here in the USA, with caches disabled, I 
come in at just under 3 seconds, and most of the times, it's around 2s. That 
depends on which page I'm using, of course, but I typically am using the Issues 
list and associated pages and the Agile boards. Because we are but a tenant in 
a larger JIRA instance, there's little we can do about the instance itself. One 
could file an INFRA ticket, I guess, but I'm not sure that they can do much 
since there can be so much variability between ISPs and such. 

# Those items in the header do relate to Cordova for those of us who manage and 
work on fixing bugs. I use those menus quite often (except for service desk). 
Users who need to search for bugs should probably use the Search box (although 
they may need to eliminate projects other than Cordova). There is an option in 
JIRA to create issue collectors, but not sure how much use that would be since 
users would still need to search for issues in the first place. It might not 
hurt to add additional documentation to the Cordova website on how best to 
search for issues, either. 

# There was a time when versions were unambiguous because everything was 
synced. When component versions were desynced that's when the version numbers 
became a bit... messy. Ideally, I guess, version numbers would include the 
component (a bit like platforms are doing, e.g., cordova-ios@4.3.1), but all of 
this assumes that reporters would actually use it (most reporters are going to 
expect a version of the form X.Y.Z, not component@X.Y.Z). Regardless, not my 
call to make. I don't see any way to change what JIRA displays on the pages you 
mentioned, though, so although the categories may not be terribly useful, I 
don't see a way to change the display either. Side note: You can create your 
own dashboard to see what is important to you, which I've done. New users 
aren't apt to do that, granted, so it's of little benefit to them.

Ultimately, I'm with you: I'd much prefer GitHub issues. We'd have more control 
and, I think, more engagement. But thus far that has proved elusive, and so we 
can only do with what we have. If there were more time and volunteers, some 
things could be cleaned up, but I think we would need more people to commit to 
that. Most of us are fighting other fires elsewhere. 

(Oh, and honestly: thank you for taking the time to report your findings. If 
you have more suggestions, please add them; even if we can't do anything about 
them, at least we have something to point to that says "these are pain points 
for our users" and work to ease the pain where we can.)

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> 

[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-04-19 Thread Jan Piotrowski (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975225#comment-15975225
 ] 

Jan Piotrowski commented on CB-12670:
-

> Speed: Can you be more specific about what you find to be slow? Specific 
> pages, workflows, etc.?

Everything. I am in Germany, and none of the pages load in <3 seconds. It's 
worst on pages that have several "components" like the issues list page where 
it first loads the issue list, then the header, then finally the first issue 
that is shown. Here is an example: 
https://www.webpagetest.org/result/170419_X9_17H6/

> Header: Can you clarify? I'm not sure I follow you here.

Imagine you are an Ionic user that just discovered it uses Cordova under the 
hood and now has a problem and wants to find out if there is already an issue 
for it. He lands on an issue page like this one and then has these links in the 
header: A "Dashboard" dropdown that has nothing to do with Cordova, "Projects" 
where the only selection is Cordova (where he already is), "Service Desk" that 
has multiple selections but none that are relevant in any way, "Agile" where 
there is a "cordova 7" board somewhere but it is hidden between all the others. 
Know what I mean?

> Component descriptions: fair enough; done. (Only a few were missing; easy 
> enough to update.)

Great!

> Versions: Since versions can apply to so many components, Descriptions and 
> release dates can't be applied to every single version. 

Aren't they quite useless then? This version filter throwing multiple 
components together that "share" a version number doesn't help at all, only 
when combined with an additional Component filter - but this is not surfaced 
anywhere.

> Would be nice to update those that are unambiguous, though. The catch is 
> finding the time to go through and update things. 

Exactly :/

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org



[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

2017-04-19 Thread Kerri Shotts (JIRA)

[ 
https://issues.apache.org/jira/browse/CB-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975116#comment-15975116
 ] 

Kerri Shotts commented on CB-12670:
---

Thanks for your suggestions. My thoughts below.

Speed: Can you be more specific about what you find to be slow? Specific pages, 
workflows, etc.?

Header: Can you clarify? I'm not sure I follow you here.

Cleanup:
- Component descriptions: fair enough; done. (Only a few were missing; easy 
enough to update.)
- Versions: Since versions can apply to so many components, Descriptions and 
release dates can't be applied to every single version. Would be nice to update 
those that are unambiguous, though. The catch is finding the time to go through 
and update things. ;-)

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org