Our changes being reviewed have multiple authors. Is there a way to specify multiple authors? If not, perhaps you will change the UI to support multiple authors just like the reviewers field supports multiple reviewers.
Hi @Scott Suppan,
Fisheye/Crucible only supports one single author.
The authors in Crucible page (https://confluence.atlassian.com/crucible/authors-in-crucible-298977326.html) provides more context on the expected usage of this field:
"The author is the person primarily responsible for acting on the outcomes of the review. In the vast majority of cases the author will be the person who made the code change under review."
Since this is not a common request, could you please help us in understanding the workflow that would benefit from this? What is currently not possible because of the availability of a single author?
Caterina - Atlassian
I understand what the primary author is in this context however our projects don't exactly working like that.
We are conducting reviews at the end of each sprint in our mobile development. We have multiple authors contributing during that sprint. One author is working on business logic while another is working on user interface controls and another is working on the web portal which accompanies the mobile app. As a result, the code is reviewed in a branch and has different authors.
While one author might be the "main" author, he cannot necessarily comment on some of the defects mentioned because he is not an expert on that subject. So he would like the other authors to comment. The tool prohibits that because they are not part of the review. In order to work around this prohibition, I have to make them reviewers just so that they can comment. While this works, it can be confusing since they are really authors in addition to one chosen as the main author.
You might advise us to have multiple smaller individual reviews but then that takes some of the code out of the context for us. The code is better understood in the context of the stories worked off in that sprint.
I think it would make your tool more flexible to permit multiple authors. Surely, this would make the tool stand apart from pull requests.
It is never about setting up a process and being done with it. Rather, the focus should always be on optimizing it for the best outcomes. Thus, we didn’t stop at setting up JSM for our recruitment pr...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events