at our company we want to implement a project template for our company which produces custom automation machines.
It should cover following project milestones (only the first 3 are described to simplify our requirements):
I am planning on creating a custom project template (with Atlassian SDK, plugin development) and an issue workflow where statuses would be the milestones. The project would only have one issue with this workflow.
Would it be then possible to display different fields / buttons on the issue during different stages (statuses) of the project (JIRA issue) ?
Also it is very important, that some of the milestones be planned for specific dates which will be specified at the JIRA project creation (and possible to be changed later).
Thank you very much for any ideas, suggestions!
Apparently this still ís a live question. If I understand your question well, you want to set up an entire out-of-the box repeatable project methodology and framework, including standard work breakdown, document templates, work tracking, probably reporting and so on.
As @Matthew Wong has described, part of that can be done with what the core of Jira really rocks at: tracking tasks through a workflow you design to your process.
Often in automation companies / projects there is a standard breakdown of tasks. And I know from experience there can really be many. Jira can be extended with apps from the Atlassian Marketplace to extend the functionality into areas you would never imagine.
Valid options for your specific use case might be to define a Template Project with your default issues already in there, so you could just copy it (complete with issues and default configuration) at the start of a new (business) project using Scriptrunner. Or you could consider creating a work breakdown template using Structure.
As you describe your story, I know for sure there's much more to it. For as soon as you create your project, the very next thing is how you are going to track progress, make sure you deliver on time. Maybe even follow up on time spent and budget. Can this all be done with Atlassian tools? Definitely, especially with the right choice of apps on top.
Given your scenario, my advise would be to talk to an Atlassian Solution Partner near you to discuss your process and help you find the right solution to your challenge. It should be a really valuable investment.
Thank you Walter, as I am a programmer, I want to use the Atlassian SDK (have already played with it) and develop some functionality myself.
I have already bought Gantt Chart Module from BigPicture. I intend to create a default project with subtasks for each milestone - so that they can be "tracked" in the Gantt Chart with appropriate milestone dates.
I'm not sure if this is still a live question for you but the scenario described is not uncommon. Many teams will track a project through a workflow while managing the actual project's work in a separate project.
That said, I don't think any custom project template will be necessary for you through SDK. You can just as easily create your workflow in a standard Jira project and create from shared configurations to minimize the amount of work you'd have to do to get a repeatable project configuration up.
With regard to your question - yes, different fields can be designated to appear at particular points in time during an issue's lifecycle. You can create screens for particular transitions so that those fields are only available for input at particular moments in time. In terms of what buttons are available, this will be contingent upon what transitions you make available from one status to another. If you make it possible for a status to transition into three others, then you'll see buttons to correspond to those actions. If you restrict the transition only to one additional status, then you'll only see one potential action to take.
Each individual transition in a workflow comes with the option to associate a specific screen. So every single step from one step to another can have a different screen and set of fields on that screen.
So for each transition:
And if you can reuse a screen for different transitions / workflows (because they require the same fields), definitely do so!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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