On Tue, Mar 3, 2015 at 3:44 PM, Fathima Dilhasha <[email protected]> wrote:
> Hi, > > Following are the points raised at $Subject. > > 1. Current "IssueTrackerConnector" needs to be replaced with an interface > to allow different issue tracker connector implementations (e.g. JIRA, > default,..etc.) . > Related class diagram is attached as "ClassDiagram_JIRAIntegration" > > 2. Application specific details for Issue Tracker can be included in > "application.rxt" > Lets use a different rxt. Lets define one for app specific infrastructure. thanks, dimuthu > > > 3. Default Issue Tracker will be created for all the applications at > Application Creation time. When user visits the Issue Tracker page, user > can configure JIRA as per the requirement. Configuring JIRA can > be done only by the Application Owner, > > User Interface design is attached as "UIDesign_JIRAIntegration". > > Please point out anything I have missed or got wrong. > > Thanks. > > Regards, > Dilhasha > > > *M.N.F. Dilhasha* > Software Engineering Intern | *WSO2 Lanka* > > email : > *[email protected] <[email protected]>*mobile : +94 77 8449321 > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: [email protected] Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
