enhancement
avatar Bakual
Bakual
8 Sep 2014

Based on some discussion in JCMS email list: https://groups.google.com/d/msg/joomla-dev-cms/tGmnQGqNu0Y/MoYNMUWzQ28J

The status "Open" conflicts with the GitHub status which is also called "Open" and contains all open issues/PRs, while our "Open" would actually only mean "not yet confirmed issues".
That leads to some confusion in the UI of JIssues.

The proposed solution would be to rename our status to "New" which would indicate that it's a new issue which needs to be confirmed first.

avatar Bakual Bakual - open - 8 Sep 2014
avatar b2z b2z - change - 8 Sep 2014
The description was changed
Labels Added: enhancement
avatar b2z
b2z - assign - 8 Sep 2014
Assigned to b2z
avatar brianteeman
brianteeman - comment - 8 Sep 2014

I assume that this mean a jissues bot to set the status to new on all new issues which dont have a status already set

avatar mbabker
mbabker - comment - 8 Sep 2014

I think we just change Open to New in our status table and we're good to go. That row is already the default value for opened items.

Unrelated but it just dawned on me, merged PRs shouldn't always get set to Closed.

avatar b2z b2z - close - 8 Sep 2014
avatar b2z b2z - close - 8 Sep 2014
avatar b2z b2z - change - 8 Sep 2014
Status New Closed
Closed_Date 0000-00-00 00:00:00 2014-09-08 19:22:43
avatar elkuku
elkuku - comment - 8 Sep 2014

Doesn't the close state also conflicts with GitHub's "close"?

When a closed issue is re opened from GitHub - to which state do we set in in our application?

Not sure what the problem is that you are trying to solve. I didn't follow the G-Groups discussion but from reading it it seems that there was a confusion because of the filter that was not working properly.

Would renaming open to new solve some (human) problem?

avatar b2z
b2z - comment - 8 Sep 2014

@mbabker please rename in DB thanks ;)

avatar b2z
b2z - comment - 8 Sep 2014

Would renaming open to new solve some (human) problem?

Exactly ;)

avatar brianteeman
brianteeman - comment - 8 Sep 2014

Yes it will make the thing work.

On 8 September 2014 20:23, Dmitry Rekun notifications@github.com wrote:

Would renaming open to new solve some (human) problem?

Exactly ;)


Reply to this email directly or view it on GitHub
#481 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar Bakual
Bakual - comment - 8 Sep 2014

Doesn't the close state also conflicts with GitHub's "close"?

Only if we have multiple states for closed ones. Like "merged", "not a bug" and similar. I don't think we have those at the moment.

avatar mbabker
mbabker - comment - 8 Sep 2014

They're all in there, just unused by the automated stuff.

avatar Bakual
Bakual - comment - 9 Sep 2014

They're all in there, just unused by the automated stuff.

Crazy, didn't know the status filter actually changes based on the "Open/Close" toggle! Awesome stuff :+1:

avatar b2z
b2z - comment - 9 Sep 2014

If you feel that "Closed" status also should be renamed - do not hesitate to open a new issue :smile_cat:

avatar b2z
b2z - comment - 11 Oct 2014

Joomla! Logo JTracker Status Comment


issues.joomla.org/tracker/jtracker/481

Easy: No
Successfull Tests: 0
Unsuccessfull Tests: 0


Last updated on 11 Oct 2014 19:53:46 GMT

Add a Comment

Login with GitHub to post a comment