We are using JIRA and actually planning to use in a new company but we need the following:
I know I can create a workflow to be used on projects but we would need "project admins" to tailor workflows on a project level. E.g. a project leader A might custom a system workflow differently than a project leader B. Of course it would require to be project-limited.
No. You need full admin rights to be able to edit workflows. Being able to delegate permissions like this is a long-standing item on Atlassian's to-do list and although they've recently made some positive noises about tackling it, we still don't have a timetable for it.
There is one option though - if you have JIRA Software, an admin can change the projects behind a board to use "simplified workflow". The project admins can then change the workflow (to a limited extent)
One word of caution here. If you make too many customised workflows the challenges of upgrading may become more complex. I would try to ascertain if there is a happy medium of maybe 4 or 5 variants that would cover most of what each project administrator would like. Unless of course you are using JIRA Software where each project can define (within limits) its own workflows.
Yes, JIRA Software lets the project lead add and remove status. They don't get access to transitions, and all the status are accessible from anywhere (you can go from any status to any other - if you have a fixed route process, this option is not for you)
JIRA Software is an application that runs on top of JIRA Core. It adds a load of functionality, but essentially, most of it is "Boards" which are an alternate view of your issues, with issues laid out as cards in a set of columns that are based on the issue status. There are Kanban and Scrum boards implemented for supporting those Agile ways. The intention of the simplified workflow is to allow your project owners to define their own boards completely, rather than have to rely on the administrators to set it up for them, and that means they need the ability to dictate the list of status they want in their workflow. So, if you want 6 columns, you define a workflow with six status. (Columns can contain more than one status, but most people keep a simple 1:1 mapping)
Ah, hang on, you don't need to do anything yet. It's not quite what I'm about to say, but you can think of JIRA Software as being the new name for "JIRA 7 + Agile" As you already have the Agile add-on, you don't need to do anything, you can use it already. Go to an Agile Board and click Configure, you'll find the option to "simplify" the workflow in there. You don't need to think about the transitions in a simplified workflow. As I said earlier, all status can go to any other status, it handles all of those for you.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs