This allows your work to mirror your social organization and is convenient in less cross-functional setups, as it allows for more straight forward project permission management. Team - Team based projects are another common organizational model.Releasable product - If you're a software development team looking to make heavy use of the JIRA release and versioning system, you'll want to give strong consideration to organizing your projects by releasable product or groups of work that share a common release cycle. Again, there's no right or wrong way - it's simply a matter of appropriate fit. There are a few strategies that are commonly taken with respect to organizing projects. So, how do other JIRA users organize their projects? That said, you can certainly close out and archive projects pertaining to ad-hoc efforts. as you go along in an ever-evolving endeavor. To take our LEGO analogy further, you aren't just building a stock, prepackaged castle you're adding additional drawbridges, turrets, etc. By default, you should consider projects as ongoing efforts. One last thing to note, projects in JIRA aren't by nature terminal. Projects will have their own versioning or release index, i.e.which groups of users can access the project, which issues they can see, etc. Projects will have their own permissions system, i.e.Whether they are workflows, fields, screens, etc., available configurations will be defined on a project-by-project basis based off of issue type. JIRA project issues will share common potential configurations.Simple enough, right? Beyond that, JIRA projects will stand alone in a few ways. So, for project "Lego Castle," issues will be itemized as, LC-1, LC-2, LC-3, and so on. Each issue contained within it will share a common key. If JIRA issues are a variety of different colored, shaped, and purposed LEGO pieces, projects is a box that hold them. The goal is that by article's end, you'll be making more informed decisions on plotting out your instance! What is a JIRA project?Īt a base level, a JIRA project is a grouping of work items or, in JIRA terms, "issues" that are held in common. Provide some factors to consider as you plan your projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |