| Summary: | Integration between JIRA --> Bugzilla is not available | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Karel Piwko <kpiwko> |
| Component: | Creating/Changing Bugs | Assignee: | Simon Green <sgreen> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6 | CC: | ebaak, sgreen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-01 09:22:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Karel Piwko
2011-12-06 08:55:12 UTC
(Enter key pressed by mistake) Description of problem: According to the various documentation, I haven't been able to keep a bugzilla issue informed about changes on JIRA side. Following doc https://docspace.corp.redhat.com/docs/DOC-48329 speaks only about Bugzilla -> JIRA integration. However, https://docspace.corp.redhat.com/docs/DOC-68417 speaks about JIRA -> Bugzilla calls say that there should be a field For issues where "Bugzilla update" custom field "Perform" option is checked, JIRA will propagate all status changes to the Bugzilla over RPC. I have not found such field. Moreover, it would make more sense to me to make it a property of External issue tracker on bugzilla side. Rationale: This direction is much more important then Bugzilla -> JIRA for a very simple reason. JBoss.org projects have they issues reported in JIRA and productized versions in Bugzilla. If you link to a product issue in Bugzilla an upstream community equivalent, you definitely want product to be informed about changes in community, not the other way around. Version-Release number of selected component (if applicable): Current version, expecting this to be 3.6 How reproducible: Always for JBPAPP and ORG projects. Steps to Reproduce: 1. Create a test bugzilla issue 2. Create a test JIRA issue 3. Try to get bugzilla one informed about changes in JIRA Actual results: No way how to set that discovered. Expected results: There is a way how to let bugzilla issue informed about changes in JIRA, either as a field/checkbox in JIRA or directly in bugzilla issue. Additional info: I have raised this with Vlastimil as part of ORG-1111 (the original request for two way linking). Will wait until he replies. Simon, this seems to be fixed now. You can close the issue. |