Ask HN: Anyone Replace Jira with GitHub Issues?

Post by dzhiurgis » Fri, Mar 24, 2023, 1:12 AM UTC

ozim wrote: post #9

genmud wrote: post #2

I guess one question is, why don't you want people to have read access to the code? IMHO if they aren't trustworthy to view code, they probably aren't trustworthy to be submitting tickets (or employed in any other roles in the org as well). To actually answer your question, you can have projects that span multiple repos, but you can't have repos that only have permissions for issues. In my org, we have a few differen…

I might be security LARPing but if someone doesn’t need to read the code to be able to do his job he just shouldn’t have access to do it. Person might have been trustworthy when they were hired and they might change their mind at some point. Even better - they still might be trustworthy but their computer got compromised and someone might be using them. Maybe some other employee has problems with them and since they…

Post by atonse » Fri, Mar 24, 2023, 1:37 AM UTC

dzhiurgis wrote: post #11

ozim wrote: post #9

Earlier quoted context omitted.

I might be security LARPing but if someone doesn’t need to read the code to be able to do his job he just shouldn’t have access to do it. Person might have been trustworthy when they were hired and they might change their mind at some point. Even better - they still might be trustworthy but their computer got compromised and someone might be using them. Maybe some other employee has problems with them and since they…

Kinda get your sentiment, but you missed parents point. Whoever creates tickets SHOULD be able to at least skim code, do basic PR reviews, test a build. "I create tickets only" sounds like a toxic role.

Post by genmud » Fri, Mar 24, 2023, 3:23 AM UTC

ozim wrote: post #9

genmud wrote: post #2

I guess one question is, why don't you want people to have read access to the code? IMHO if they aren't trustworthy to view code, they probably aren't trustworthy to be submitting tickets (or employed in any other roles in the org as well). To actually answer your question, you can have projects that span multiple repos, but you can't have repos that only have permissions for issues. In my org, we have a few differen…

I might be security LARPing but if someone doesn’t need to read the code to be able to do his job he just shouldn’t have access to do it. Person might have been trustworthy when they were hired and they might change their mind at some point. Even better - they still might be trustworthy but their computer got compromised and someone might be using them. Maybe some other employee has problems with them and since they…

Post by Aperocky » Fri, Mar 24, 2023, 3:44 AM UTC

isopede wrote: post #10

shoo wrote: post #3

what's your underlying motivation to eliminate jira & notion?

Among others, regulatory reasons can mean Jira is not an option (medical, financial, export controls etc). They removed their self-hosted version a while ago, and their "data center" version is a $42,000 _minimum_.

Post by systemvoltage » Fri, Mar 24, 2023, 5:36 AM UTC

genmud wrote: post #2

I guess one question is, why don't you want people to have read access to the code? IMHO if they aren't trustworthy to view code, they probably aren't trustworthy to be submitting tickets (or employed in any other roles in the org as well). To actually answer your question, you can have projects that span multiple repos, but you can't have repos that only have permissions for issues. In my org, we have a few differen…