-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
149
-
1
-
p4 2011.1 introduced a new feature called "streams" which is similar, but not the exactly the same as a branch. while fisheye will index commits on a "streams" depot, the streams will not be recognised as separate branches.
we should be checking for streams as well as branch specs when indexing commits.
a current workaround is to create branch specs to match the streams.
----------------
here you can see the commits that were actually made:
And the fact that all commits appear on the "head" branch:
Using the workaround, i created 2 branch specs:
MAIN (//depot/... //depot/MAIN/...)
DEV (//depot/MAIN/... //depot/DEV/...)
The commits are now represented in the following way (note the DEV branch spec):
And they appear like the following when browsing in FishEye:
![]() |
![]() |
- is duplicated by
-
CRUC-8302 Improve Crucible experience with perforce streams
- Closed
- mentioned in
-
Page No Confluence page found with the given URL.
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
Hi everyone,
thank you very much for reporting this suggestion and your involvement in the conversations around it. This suggestion is in the 'Reviewing' state which means it awaits assessment by our team.
As Fisheye and Crucible have entered basic maintenance mode, our team currently focuses more on bug-fixes and platform updates rather than on feature development. We may still deliver some small improvements if they fit into the maintenance theme. However, suggestions which have been assessed already and are in the Under consideration state have higher priority.
It means it may take time until we review this suggestion and decide whether to put it on the roadmap or reject it. You can expect an update from us in couple of months. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Kind regards
Marek Parfianowicz
Development Team Lead
Fisheye/Crucible Team