Ajith developed an error reporting component recently. May be you can reuse it. Ajith please confirm.
Thanks, Sameera. On Sunday, March 6, 2011, Hasini Yatawatte <hasi...@wso2.com> wrote: > > > > > > > > > Hi devs,These days I am working on a new carbon > component for tracking issues. The main objective of this is to allow > users of our products to report issues to JIRA and retrieve status of > issues reported through the product itself. > > > > The design of the component is as shown > in the following diagram. FE sends a request to report an issue to BE > where the BE connects to the issue tracking system via an adapter > implementation. Currently I have implemented the adapter to JIRA > only. I am hoping to implement it to support Bugzilla as well in the > future. > > > > > > > > > > > > > The features of this component are as > follows.Multiple JIRA multiple user > scenario > Users can add multiple JIRA account > details (eg: private, public, support etc) and corresponding > credentials which are stored inside an embedded registry. > Credentials are validated before storing and there is an option > to > edit them after wards as well. Hence when creating an issue > user is > not required to provide credentials again, rather its just a > matter > of selecting the JIRA account from a drop down list.Reporting > issues. > - Users can report issues to > multiple JIRA accounts. > - Unlike creating issues from > JIRA interface directly, here user need not to specify operating > environment details. Rather they are automatically captured from the > BE. > - Issues are assigned to project > lead automatically.Retrieving issues > Users can view issues reported by > him/her self for a selected JIRA account. > > > > > > > > > What I have done so far - Implementation comes as 5 > modules > > > > > > > > > > > 1. Issue tracking adapter API > Adapter implementation for > JIRA > Back end component consisting > admin service > Front end component > common component to provide > utility methods and common > functionalities. > > > > > > > - Component is listed under Tools > menu as follows. > - FE and BE functionality of > handling multiple JIRA accounts, validating credentials, putting and > getting them as registry resources are done. - FE and BE > functionality for > reporting issues from multiple accounts is done. - Retrieving > issues reported by an > user is done. > > > > > > > > > To Dos :Handling attachments when > reporting an issue. > Displaying issues in a paginated > manner.Applying a user based permission model to resources > stored in registry. > Any comments on this are highly appreciated. > > Thanks, > Best Regards, > > -- > Hasini Randika Yatawatte, > Software Engineer. > WSO2 Inc. > -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware _______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
