Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot edit an issue after posting unless I go to Github. #940

Open
uglyeoin opened this issue Jan 26, 2017 · 4 comments
Open

Cannot edit an issue after posting unless I go to Github. #940

uglyeoin opened this issue Jan 26, 2017 · 4 comments

Comments

@uglyeoin
Copy link

If you are submitting an issue for the Joomla! CMS, please submit it at https://github.com/joomla/joomla-cms/issues/new instead. You may remove this line from the issue template.

Steps to reproduce the issue

Submit an issue/comment on an issue

Expected result

I want to edit my comment or issue

Actual result

I can edit on Github but it remains incorrect on issues.joomla.org. It would be great to be able to edit the issue.

System information (as much as possible)

Additional comments

@mbabker
Copy link
Contributor

mbabker commented Jan 26, 2017

Usually edits come in from GitHub pretty quickly thanks to webhooks and our cron jobs, but you're right that an edit feature in general is missing that's comparable to GitHub.

FWIW we do have a full issue edit page for certain ACL groups, we might want to look at expanding its use to include an "edit own" style check letting someone edit the base data they submitted regardless of their ACL role.

@uglyeoin
Copy link
Author

In which case are we saying we don't want people to use issues.joomla.org because they may as well use Github? I'm trying to encourage people to submit issues and resolve them and it's a little confusing as to which way is the preferred way at the moment.

@mbabker
Copy link
Contributor

mbabker commented Jan 27, 2017

Either one works, both end up with the same information. The basic difference is the tracker has categories, status tracking, the tests widget, and a way to give users (mainly bug squad members) permissions to manage items on GitHub through its API without giving everyone full management access on the repo.

@uglyeoin
Copy link
Author

Ah I see, ok got it. Very clever stuff. Ok well my issue is neither here nor there, if it's in any way difficult then other things should be prioritised instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants