-
Bug
-
Resolution: Fixed
-
Medium
-
8
-
Minor
-
1
-
Issue Summary
Jira Activity Stream gadget does not show all information in some cases, and the return is “user has had no activity”.
Instead of trying to get activities for chosen filters, it gets the by max results, then apply the filters later. So the entries will be missed if they are out of the limitation.
Steps to Reproduce
These steps are reproduced by the team's Jira dashboards in a test environment.
- If we configure the activity stream gadget limit to 4 items without any filters, then the request is like this: https://endeavour-demo.jira-dev.com/plugins/servlet/streams?maxResults=4&relativeLinks=true (I call this as request 1)
- If we add a filter for Account ID to a user, then the request gonna be like this: https://endeavour-demo.jira-dev.com/plugins/servlet/streams?maxResults=4&relativeLinks=true&streams=account-id+IS+655363%3A110b9b2e-4adb-41f7-9b2c-1dcca936ae1e (I call this as request 2)
- So you can see the difference in the request url, it has the account id in the request 2.
- So as the normal logic, we would expect the request 2 will return a list with 10 activities from the selected user, right?
- But this is not how the current way it's working.
- For example, if the request 1 returns something like this:
- Activity 1 from someone else
- Activity 2 from someone else
- Activity 3 from selected user in request 2
- Activity 4 from selected user in request 2
- Then the request 2 only return 2 activities, which is Activity 3 and Activity 4.
- Let's give another example for request 2 but limit to 2 items: So we would expect request 2 is not still return Activity 3 and Activity 4.
- But the bug is request 2 is now return empty result, this is because activities from selected user (which is Activity 3 and Activity 4) is the third and forth entries, but we only limit to 2 items.
Expected Results
When adding a user, all the activities of that user appear, but in some cases appear “user has had no activity”
Actual Results
Mentioned above.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-75065 Activity Stream gadget not working on a single user filter
-
- Closed
-
- relates to
-
JRACLOUD-79287 Activity Stream: Issue Key is only post-processed, but not included in the request
-
- Closed
-
- added to idea
-
DAG-300 Failed to load
- is resolved by
-
DAG-298 Failed to load
Form Name |
---|
This is still broken in my company's new Jira since we transitioned after a buyout. I just set up an activity stream to filter by my own Account ID only and I am still seeing everyone's work in the stream.