a bug, a task, or another issue type in your project. Different organizations use Jira to track different kinds of issues. It can range from representing a single unit of work, like a simple task, to a larger parent work item to be tracked, like a story or an epic. ...
Option #2: use Hierarchy for Jira to create an epic > story > task hierarchy An epic > story > task (or epic > story > task > sub-task) hierarchy has two levels which can be added to sprints: stories and tasks.This gives you the flexibility to add stories directly to sprints or...
Flexibility:With some work, Jira’s issue templates can be adapted to include various custom fields. This feature allows the creation of specific custom issue types such as ‘Exploratory Test’ or ‘Regression Test,’ distinct from Jira’s default issue types (like Epic, Story, Task, Sub-Task...
Why is history lost when you move an issue? When I move an issue from one project to another, the screen definitions have the same information, but the work flows are different. However, when I move them, the history of any changes/updates tha... ...
Transition: A transition represents the action being taken to move an issue from status to status. A transition is a one-way link, so if an issue needs to move back and forth between two statuses, two transitions need to be created. ...
subtasks are connected with one another. With a timeline view, project managers can adjust schedules if a problem arises in one task that will impact others. To get this type of functionality, you’d have to get a separate Gantt chart app and connect it to Jira through the Atlassian ...
Task- A task that needs to be done. Subtask- A small task existing with a large chunk of work. Default Issue Types in JIRA Software Story- A story is a functionality request expressed from the user's perspective. Bug- A bug is a problem that impairs service or product functionality. ...
Hi, with Jira Agile I am forced to move from task-subtask concept to epis-issue concept(I am really not very happy with that). But real blocker
The move command lets you transition an issue from one state to another.# Move an issue using an interactive prompt $ jira issue move # Pass required parameters to skip prompt $ jira issue move ISSUE-1 "In Progress"If your workflow allows to add comment, resolution or assignee while moving...
{ "fields": { "project": { "key": "TEST" }, "parent": { "key": "TEST-101" }, "summary": "Sub-task of TEST-101", "description": "Don't forget to do this too.", "issuetype": { "id": "5" } } } ResponseThe response provides the sub-task ID, key, and the URL to...