Ability to write github comments as org mode instead of markdown
New GitHub Issues Beta
201–210 of 223 posts
Re: New GitHub Issues Beta
#202Re: New GitHub Issues Beta
#203Re: New GitHub Issues Beta
#204Re: New GitHub Issues Beta
#205Earlier quoted context omitted.
Ex-Atlassian here. Last day was around a month ago. Not tense at all. You'd be surprised at how many people actually like Jira, mainly because of how customizable it is. That in my opinion is it's biggest boon and its greatest curse. Every Jira instance is so different it's hard to compare between them. Stock isn't bad at all and works quite well. There are performance issues for sure, but I've yet to see a competito…
> You'd be surprised at how many people actually like Jira, mainly because of how customizable it is. Are there any numbers of how many of the users like it, compared to how many users struggle with it? I can't imagine that a majority of Jira users likes it, as that's not my experience. I have met very few people (mainly project managers) so far, which believe that Jira (and other Atlassian products as well) are grea…
I first started being annoyed by it when I joined a large corporation with a central department that would enforce specific workflows and processes. Now I can't move tasks into a sprint without assigning them to a person first, can't move task from status x to y and have a 100 custom fields in there. It's no fun anymore. At the same time the projects are owned by project management and it doesn't feel like home anymore. Where I initially opened up my Jira Board first thing every morning it now has become a chore.
At the same time I have to say that I kinda understand where those processes come from. I now work in an industry where accidentally using a wrong issue type or forgetting to assign issues to specific code changes can become an actual issue due to traceability requirements mandated by law.
Re: New GitHub Issues Beta
#206Why use any other Issue tracker if Github can do this itself? Countless integrations would be replaced by this. I wonder what would happen to all those dashboard / issue tracker / project tracking apps now.
Re: New GitHub Issues Beta
#207It floors me that they haven't addressed the underlying architecture issues that made Issues unusable: Issues are only for a single repo. Business users don't (and shouldn't) know what repo to add an Issue to. This is why we moved away from Issues and none of these new visualizations make the product usable until they deliver multi-repo issues.
Maybe Github Issues is not supposed to work as a support ticketing system? You are allowed to move issues between repos, so in theory you could create a dummy repo where users can add issues, and then those issues can be moved to their appropriate repo.
Just in case it did, it would radically deprecate a bunch of tools and simplify life of small dev teams.
Re: New GitHub Issues Beta
#208It floors me that they haven't addressed the underlying architecture issues that made Issues unusable: Issues are only for a single repo. Business users don't (and shouldn't) know what repo to add an Issue to. This is why we moved away from Issues and none of these new visualizations make the product usable until they deliver multi-repo issues.
GitHub issues should not be used by non-technical contributors though (imo)
Re: New GitHub Issues Beta
#209Re: New GitHub Issues Beta
#210I'll throw my random feature request in here since everyone else is: Ability to write github comments as org mode instead of markdown