This is related to Issue tracking in the project, but I want to not distract that thread. Today we already have GitHub issues in some projects and I think it can be useful to track Red Hat’s Jira there. In Redmine we already have a (deprecated) Bugzilla field and a Jira field.
Is there an objection to add a custom field for Red Hat Jira at the theforeman organization level? It needs to be a text field (URLs are autodetected).
While I hate the split of information coming from Red Hat Jira, having the reference would be an improvement in finding additional information.
As some Jira issues were not public in the past, a label or something that tells me I can skip this link as private would be nice, but I have no idea if this could be done.
I think we should still aim to have the upstream information to be complete that you don’t need Jira to understand it. The primary purpose is IMHO for Red Hatters to know if we’re already tracking it downstream.
On a related note: I’m actively thinking about how we can do a better job here. So far not a lot, but hopefully next week I can actually present something useful at DevConf.
Since it’s a text field, we can use $url (private) even if it makes parsing a bit harder. And keeping that in sync as well. I’d like to avoid it in the beginning and revisit it if it becomes a common problem.
Since there was no objection, I’ve added this field. Replace `--certificate-cname` with `--server-alias` · Issue #639 · theforeman/foremanctl · GitHub has an example.
I’d appreciate feedback if this is useful or not.
What is the main purpose here? If it’s just for tracking PR ↔ Jira relations, it may be OK just to add a prefix to PRs, like in foreman (For example JIRA-1234: fix foo for issues reported in Jira or GH-456: fix bar for issues that do not have jira attached). If we want to detect issues that are duplicated in Jira and GH - then your solution is actually a great thing, it will give everyone an indication what’s the full status of the issue.
@Shimon_Shtein I like being able to find the corresponding Jira from the Redmine without having to search for it, and this will bring that feature to Github issues as well.
@ekohl Redmine has a nice feature where we just set the field to, say, “SAT-47543” and it makes the link for you. Too bad that we can’t do that here, but just wanted to point out that difference.
That was my intention. You can now easily look for issues that have an attached issue: Issues · theforeman/foremanctl · GitHub
And I also hope we can write some more automation to cross link again. Right now I’m worried we’re tracking a lot of the containerization effort only in downstream, which isn’t great for adoption. I’d like to be more transparent again.
Guess who added that field to Redmine? 
I agree it’d be nicer to have that.