NAVIGATION
Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 Trello

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Div
classpage-wrapper
Div

This document

Note
consists of= składa sie z (krokówinstrukcje) | contains zawiera (krokiinstrukcje)

step by step instructions that

Note
can be
applied
applied  apply

both to BigGantt and BigPicture.

Warning

Due to the nature of next-gen projects, some features and functionalities of our apps remain unavailable. More details in "Missing features and functionalities" section below.

Configuration in Jira

Set up each of your next-gen projects like below:

  1. Go to Project settings > Issue types.



  2. Add Start date (by Jira) and Due date (by Jira) fields to the primary fields list of each Issue type.



  3. Create two Date-type custom fields1 which will be used for Baselines creation on a Gantt.



    1 Name them so that they consist of a key of a given next-gen project e.g. Baseline start date ( key ), Baseline end date ( key ) where "key" is a given next-gen project's key.

  4. Add these custom fields to each Issue type's primary fields list.

App configuration

  1. Go to Jira settings > Apps > BigGantt > Task configuration.



  2. In "Custom synchronization settings" push

    Note

    push the button to sie odnosi do rzeczywistych przycisków/guzików które można palcem pyrgnąć a na stronie to wszystko się klika linki batony i inne gadzetony

    click "Add Project" button. Select your next-gen project and click "Add and configure".

    Image Modified

  3. Map Start date (by Jira) and Due date (by Jira) fields to both "Task start date" and "Task end date".



  4. Map "- -" to "Task progress".



  5. Map custom fields created in step 3. (Configuration in Jira) to both "Task baseline start date" and "Task baseline end date". Afterwards Finally push "Save".

Alternative setup

You can create and use your own custom fields (local custom fields that were created in a given next-gen project) which would store information about your tasks' start and end dates. Yet, the following such a setup is not recommended2 for those who want to benefit from both the Gantt and next-gen projects' features like Roadmap.

Configuration in Jira

  1. Go to Project settings > Issue types.



  2. Create two Date-type custom fields which will be used as "Task start date" and "Task end date".



    Name them so that they consist of a key of a given next-gen project e.g. Start date ( key ) and End date ( key ) where "key" is a given next-gen project's key.



  3. Add previously created fields to primary fields list of each Issue type you have in your next-gen project. Remove Start date (by Jira) and Due date (by Jira) from primary fields list of each Issue type.



  4. Create two Date-type custom fields which will be used for Baselines creation on a Gantt.
    Name them so that they consist of a key of a given next-gen project e.g. Baseline start date ( key ) and Baseline end date ( key ) where "key" is a the given next-gen project's key.

    Image Modified

  5. Add these custom fields to each Issue type's primary fields list.

App configuration

  1. Go to Jira settings > Apps > BigGantt > Task configuration.



  2. In "Custom synchronization settings" push click "Add Project" button. Select your next-gen project and click "Add and configure".



  3. Map previously created task period fields to both "Task start date" and "Task end date".



  4. Map "- -" to "Task progress".



  5. Map custom fields created in one of the previous steps to both "Task baseline start date" and "Task baseline end date". Afterwards, push "Save".

2 Without having Start date (by Jira) / Due date (by Jira) task period mapping chosen, bi-directional task period dates synchronization with Jira won't work properly. You will still be able to use Roadmap feature, but Epics' dates won't be reflected on a Gantt's timeline and vice versa. For instance, if you have a different task period mapping and have a Program that includes several Epics in its scope (visible on a Gantt) and you move them along a Gantt's timeline wanting this change to be reflected on Jira's Roadmap, this won't happen.

Missing features & functionalities

Info
Feature requests for next-gen projects can be submitted directly in comments section of this thread (Atlassian). The full list of missing features/customers' suggestions/feature requests collected as sub-tasks can be found in the following ticket: JSWCLOUD-17392. Some useful information can also be found here and on Atlassian's public roadmap for next-gen projects, here.
App (Module)Feature/functionalityMissing due toFuture plansPreview

BigGantt (Gantt)

BigPicture (Gantt)

Color by status

Rules that have replaced advanced workflow configuration in next-gen projects.

According to Atlassian, workflow configuration coming soon. For more details, see the above notice.


BigGantt (Gantt)

BigPicture (Gantt)

Resources view

Lack of possibility to use global custom fields - Time Tracking and Story Points.

Story point estimation field available only.

According to Atlassian, time estimation coming soon. For more details, see the above notice or the following tickets.

Ticket on Atlassian's end: JSWCLOUD-17447

Ticket on SoftwarePlant's end: EXTPLATFORM-460


BigGantt (Gantt)

BigPicture (Gantt)

Synchronization:

  1. Synchronize Parent Link,
  2. Synchronize components structure,
  3. Synchronize versions structure,
  4. Synchronize subtasks,
  5. Synchronize epics.
  1. Lack of possibility to use Parent Link (global field) in next-gen projects,
  2. No components in next-gen projects,
  3. No version management in next-gen projects,
  4. No Sub-tasks in next-gen projects,
  5. No Epic Link in next-gen projects.
For more details, see the above notice.

BigGantt (Gantt)

BigPicture (Gantt)

Views of fields of Program Perspectives:

  • All custom fields (green ones) except ones created/available within a given next-gen project.
  • Jira fields:
  1. Fix Versions, Version release date, Affects Versions
  2. Status, Resolution, Resolve
  3. Time Tracking, Time Tracking Progress, Work Ratio, Original estimate, Remaining estimate, Time spent
  4. Components
  5. Attachments
  1. No version management in next-gen projects,
  2. No workflow configuration in next-gen projects,
  3. Lack of possibility to use global Time Tracking custom field,
  4. No components in next-gen projects,
  5. No attachments of Issues in next-gen projects.


For more details, see the above notice.
BigTemplate (Jira Issue Detail page)Single issue exportMissing BigTemplate's Issue export panel.Ticket on SoftwarePlant's end: PPM-5410

BigGantt (Jira Issue Detail page)

BigPicture (Jira Issue Detail page)

Status field's view within WBS Widget

No workflow configuration in next-gen projects.For more details, see the above notice.
BigPicture (Resources)Resources management

Lack of possibility to use global custom fields - Time Tracking and Story Points.

See Resources view
BigPicture (Risks)Risk matrix and Risk CRUD list 3No risk configuration per Jira project.Ticket on SoftwarePlant's end: PPM-5408

3 If mapped custom fields (local custom fields that were created in a given next-gen project) to consequence and probability fields (global settings), Risks module would work only for this particular next-gen project.

If you find this article not sufficient enough and still struggle with making your app working with next-gen projects, contact us via our Portal so we could help you out!



You are evaluating RefinedTheme.