All JIRA

In a classic Jira project there are building blocks which is required to be created and assembled to onboard a project .Those building blocks like, project, issue types, workflow, screens, permissions and notifications are independent entities. They do not converse with each other. E.g.,  Team A has created a Jira project as "Legos" and two issue types are decided "Story and bug" to be tracked. The team has also gone ahead and created two workflows for Story and bug.  Now as these building blocks are created, they are independent, The issue types chosen will not reflect under the project or the issue types will not traverse as per the workflow, because they are not linked to one another "Schemes" are used to assemble these building blocks.  Each of the blocks here will have the separate schemes created and integrated. This blog shares details on the concept, creation and linking of each schemes to the project Issue type schemes Issue types are the list of ...

JIRA - Originally a bug and Issue tracker has evolved into a powerful work management tool.  JIRA is built on a concept that allows users to design their own delivery solution model . Various parameters of JIRA, like workflows, screens, notifications, permissions and so on can be customized to our model Of all other parameters, "Screens" are visible and interactive to the end user. Designing of screens should be more thoughtful to ensure better experience . Sharing you, the WHAT, WHEN and HOW technique for JIRA Screen design WHAT data to collect While you design a screen,  the first step is to understand and consolidate all the information required for the issue type  For e.g. Story Vs Defect Story = Epic details, Story points, effort, Dependencies, Feature,etc., .  Defect = Severity, priority, Affect version, fix version, Impact details,etc., Consider gathering Information from various sources, to ensure maximum coverage. Following are few of the sources which you c...