Hi community,
I have tried to search any documentation regarding the behaviour of this custom field without any success.
I want to know how does this field behave in use. What difference make if this field is populated?
Any information would be appreciated.
Thanks!
Jira already supports per user Activity Feed. Isn't that sufficient for your usecase? It is accessible at <yourjiraurl>/secure/ViewProfile.jspa?name=<username>.
The same could be accessed via RSS at <yourjiraurl>/plugins/servlet/streams?filterUser=<username>
Activity Feed sounds good. Would that include - User name, date, issue description, team assigned etc. We actually want to capture what kind of issue are being in submitted in JIRA and who are the people assigned to work on these? Will Avtivity Feed give me all this information?
Thanks for your inputs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Creation, comments, and assignment are part of the user feed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you share some link for more details/demo ofActivity Feed. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does this answer your query? http://confluence.atlassian.com/display/JIRA/Adding+the+Activity+Stream+Gadget
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This seems to be what we are looking for. Might need to tweak it a bit though..
Thanks a ton!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you apply a filter to this, to get activites only in requested time?
/secure/ViewProfile.jspa?name=<username>.....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could develop an event listener in JIRA that catches all events like isue create, issue close, assign and update a shadow record in your current support system. Of course your curren support system needs to provide a remote API (REST, Soap) that you can use to create, update and delete work items there.
Of course this is said easier than done but we have done something similar. Our leading support system get's reported issues from various sources, one of them is JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your inputs. Would love to explore it further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.