[
https://issues.jboss.org/browse/JBDS-1505?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1505:
----------------------------------
Given we're a lightweight / agile / understaffed team, why not just have an internal
JIRA instance installed? That way it's the same technology being used elsewhere
(rather than having to learn, maintain, and support some other system) and it's the
same support/infra needed from IT ops to keep it running.
Even better would be if the same authentication could be shared so that my login for
issues.jboss.org (public) would work for this new hypothetical
issues.jboss.com (internal)
instance. Conversely, customers on
jboss.com could log in to
jboss.org and help w/ issues
reported there, and they too wouldn't have to learn a second technology.
IMHO, you'd get the benefit of an "internal" and
"customer-branded" version while keeping the overhead low and the integration
options high.
Also, if you build an Eclipse/JBDS plugin that integrates w/ JIRA, you could use if for
both JBoss Tools (community testing & reporting) AND JBoss Developer Studio (customer
issue reporting). Oh, and FWIW, such integration already exists (at least partially) -
using the Mylyn Atlassian JIRA connector:
http://confluence.atlassian.com/display/IDEPLUGIN/Working+with+JIRA+Issue...
http://help.tasktop.com/help/topic/com.tasktop.help.ui/userguide/partners...
http://www.tasktop.com/mylyn/
$0.02,
N
allow users to submit problem reports from JBDS
-----------------------------------------------
Key: JBDS-1505
URL:
https://issues.jboss.org/browse/JBDS-1505
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: integration
Affects Versions: LATER
Environment: All
Reporter: Andrew Hecox
Fix For: 4.0.x, LATER
user-story: as a JBoss customer, I can create a report a problem from JBDS and instantly
get suggestions back so that I can easily get help solving the problem I'm working on
in my editor
notes: I think something which allowed a user to create a problem report, as well as send
any applicable files, with us sending back instant results (and prior to case creation)
would be a good value add to JBDS. We don't yet have a public API for this, but
something would be added to our subscriber API:
https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/
probably RESTfully modeled in it's own root level domain, eg, /problem or
/problem_report, /report, etc... with a synchronous response including suggested KBase
articles, community forums, whitepapers, etc...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira