HI Sumedha

Hope to make improvements on the gadget in the future and i hope
Nuwan answered all your questions. thanks for the feedback

On Fri, Apr 1, 2011 at 4:37 PM, Nuwan Bandara <[email protected]> wrote:

> Hi Sumedha,
>
> First of all the gadget is far from perfect to be added to the client
> portal as it is. This was pulasthis 1st assignment, simply to understand how
> gadget authoring works, consuming REST/JSON etc but with the intention of
> making it useful for our ongoing work at the sometime.
>
> On Fri, Apr 1, 2011 at 4:10 PM, Sumedha Rubasinghe <[email protected]>wrote:
>
>> Pulasthi,
>> Good work..
>>
>> What are the advantage of these gadgets over the ones provided by JIRA
>> itself? (apart from the fact these can run within our platform.. of
>> course)... If these are going to the client portal, I would say we need to
>> show more summarized view.
>>
>
> At the moment Jira provides alot of gadgets, but sadly non of them are
> portable (We can use them in our dashboard or not even in iGoogle). Even
> though they have used the gadget spec they are using some custom shindig
> features which perform all the communication.
>
> Few advantages are that this gadget can be used in our dashboard or in
> iGoogle. The gadget is not written only to disply our issues, the use can
> give any jira project URL, and retrieve the projects and other information
>
>
>>
>> IMO, the idea is for a client to see a summary of their projects using the
>> portal & the go to the client support jira for more details if required.
>>  Considering the user base, manager type of roles will be interested in
>> getting the summarized view, where as engineers would like to go to the
>> actual jira.
>>
>
> Yes I agree, still the gadget does not handle any authenticated user based
> filtering, I believe pulasthi will improve this with the suggestions.
>
>
>>
>> Have you also considered the project summary view offered by JIRA itself?
>> Have we considered the option of JIRA's gadgets rather than writing our own?
>>
>
> Yes I have tried to use JIRA gadgets, but failed due to the custom features
> they use. However with the REST API and the gadget development api they are
> offering with Jira 4.2.2 update we can write much better gadgets. Hope this
> will be considered when the Jira system in being updated (I did comment of
> Jira update mail about this too)
>
> Thanks & regards,
> /Nuwan
>
>
>
>>
>> /sumedha
>>
>>
>> On Fri, Apr 1, 2011 at 1:52 PM, Pulasthi Supun <[email protected]> wrote:
>>
>>>  HI All
>>>
>>> I created a new JIRA issue tracking gadget for the Gadget server under
>>> client information portal which i am assigned for my internship. This was
>>> developed since the existing JIRA gadget supply's very little functionality.
>>>       When developing the gadget i looked into a few JIRA API's including
>>> SOAP, XML-RPC and REST. Since the JIRA REST API is still not complete and
>>> was only supported in JIRA 4.2+ it was decided on retrieving the data needed
>>> by gadget using  the "searchrequest-xml". This request will send back and
>>> XML containing the issue data filtered by the parameter that are set in the
>>> request.The XML is parsed to generate the view. The view is generated using
>>> JQuery and JavaScript.
>>>
>>> Features:
>>>
>>> 1.Users can browse the issues related to a project by selecting the
>>> project from the drop down menu
>>>
>>> 2.Users can use the search option to search the issues in JIRA according
>>> to the following parameters
>>>
>>>    - project (one or many)
>>>    - issue type (one or many)
>>>    - status  (one or many)
>>>    - resolution  (one or many)
>>>    - priorities (one or many)
>>>    - reporter
>>>    - assignee
>>>    - users can also use a text search to find a specific string within
>>>    comments,summary, description and environment
>>>
>>>
>>> 3. Users can specify the organization in the gadget settings to use the
>>> gadget for an organization of their choice
>>>
>>> This gadget will be available with the next Gadget Server release.
>>>
>>>  below are some snapshots of the gadget
>>>
>>>  [image: snapshot01.PNG]
>>>
>>>
>>> [image: snapshot2.PNG]
>>>
>>>
>>> [image: snapshot3.PNG]
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> Nuwan Bandara
> Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://www.nuwanbando.com
>
> <http://www.nuwanbando.com/>
>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to