Default parameters for issue's options (BB-3526)

Issue #4903 open
Sidney Lins created an issue


It would be very very useful to have some place where we could set default options for 'assigne', 'type' and so on.

It is very boring to have to set them in each new issue.


  • Kind
  • Priority
  • Component
  • Asignee

Comments (32)

  1. Dylan Etkin

    We actually have a pull request under review to bring this back right now.

    I expect it to sit for another week or so while we get it through review but we have not forgotten this issue, I promise.

    Cheers, Dylan

  2. Daniel Bennett Account Deactivated

    As the creator of the pull request mentioned above I can say that, sadly, my changes did not make it in.

    I'm going to mark this as open so it's clear that it's still on the plan despite suffering a setback.

  3. Sidney Lins reporter

    More than ONE YEAR and it is stuck till now! Can`t understand! Hope that Atlassian Bitbucket "hear" you @ddbennett !

  4. Ed Kolis

    I have a repo where the assignee is set (using the old system when you actually could set it), and now I can't unset it!

  5. Sidney Lins reporter

    It is so hard as to put a 'selected' param in a drop down list. Almost 3 (THREE YEARS) to do it? Really??

  6. mpc

    I have to jump on the bandwagon here and throw my vote in. As an aside, I would think the default "default" would be "Task", not "Bug". Let's throw the developers a bone and err on the side of optimism.

  7. Garret Wilson

    I note that there was a separate issue for creating a default assignee, which I feel is much more important than assigning a default issue "type", but someone lumped them all together here. Fine, if Atlassian wants to implement all of them---but so far Atlassian is not implementing any of them.

    How come we can set a default reviewer for a pull request, but can't set a default assignee for an issue?

    We can't even set a default person to be notified when an issue is created!!

    (Yes, you're going to tell me that we can set an email to be notified when an issue is created, but that's different---the entire Bitbucket system works on users, not on email addresses. Now I have to go into each project and enter an email address, and if a user changes their email I have to go change all the emails.)

    In short the issue tracking system is disjointed and incomplete.

  8. Sidney Lins reporter

    It has already been past more than FOUR years since this stupidly little issue has been open without any progress.

    Things like that makes me 'loose the faith' in Atlassian, unfortunatelly.

  9. Garret Wilson

    Who "lumped them all together here"?

    @mbertrand80 and @mafrauen lumped them all together here from #5077 and #6302 and #5078.


    In 2012 and in 2013 and in 2012, respectively.

    Are you sure?

    I am only reading the historical comments in the issue tracker.

  10. Sidney Lins reporter

    So, "duplicate" has a new meaning for bitbucket team.

    From oxford dictionary: "One of two or more identical things".

  11. Log in to comment