All JIRA

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 can refer

During this pandemic, WHO and other government bodies have been giving guidelines and instructions to ensure our safety. Most people read thru these guidelines, some understand, few follow and less adhere. Even with the lesser, the effectiveness is questionable because, the guideline is just followed. With 14 years of journey with process, can't help but compare the current scenario with "Process compliance" in Software Quality Process Compliance Mishaps Process is Taken in by the team irrespective of the fitment Followed strictly (only) for sample releases to showcase it to the certification auditors Felt as an unnecessary, forced add-on to the delivery cycle An effort drainer for the software engineers Used as a weapon by senior management to punish the mistakes Do not follow Process Focus on the Process intention than the guideline - Like, review is to identify the defects early, do not focus on meeting the org target Process should be seamlessly integrated to delivery