As a work-around you can: Run a query to get your epic list. Export that result list. Grab just the keys, and convert them into comma-separated values (CSV) using a text editor. Paste the CSV epic list into your second query: "Epic Link" IN (yourCSVlist) AND labels = iPub ORDER BY "Epic Link", Key. Best regards, 1 accepted. In a project roadmap you can only see issues from that project. If you're on the Premium plan then you get access to Advanced Roadmaps - a different product (formerly Portfolio but now integrated into Jira Premium) which will allow you to arrange multiple projects/boards/filters in one view. It's pretty good, but at an added cost.
To promote a feature: On the features page, select Promote f rom the More Actions menu on the toolbar (top-right of the page). Select Feature as an object, and then select a PI and a program. Under Parent, select the feature which you want to promote to a parent epic. Under Child, select the check boxes of the features which will be child
Add an epic from the Roadmap: With the Roadmap open, select “More” (…) in the top right and then “Board settings”. From the Roadmap tab, then click to enable Epics for your project. On the left sidebar, then click Roadmap and select “+ Create epic” (if the Roadmap isn’t populated, you just need to type to add your first Epic) In
2 rules: create the epic/stories in one rule and the sub-tasks in another. rule-A: create the epic, and when creating the stories add some field value to check. rule-B: triggered on issue created, check the condition for the field value you set in rule-A, and then create the sub-tasks. Please note: in rule-B, select the option "Allow rule
Epic -> 3. In Progress Story -> 2. In Progress Sub-task -> 1. In Progress When the Sub-task is moved to 'In Progress' I would like the Story to then transition to 'In Progress' (easy, already done) AND also update the Epic into 'In Progress'. Can I create a rule to do this using Jira Automat
Tempo Timesheets focuses on the logged time (aka "Time Spent", a total of the "Worklog Entries"). The "Original Estimate" and "Time Remaining" values in Jira have value for reports and work tracking (e.g. BurnUp/BurnDown charts, Sprint/Release/Epic progress, etc). But Tempo doesn't use those two fields at all.
RaVd3.
