AIM Agile Planning for Jira

Has a few bugs, especially on tasks with sub-tasks

• 

  AIM - Agile IT Management

  Hi Médico em Casa,

  sorry that you had a bad experience with AIM Agile Planning for Jira. We always like comments that improve the quality of our apps, as they are there to help you. Would you be so nice and tell us about those bugs that you have seen so that we can take care of them? There is a Jira Service Desk available for bugs and other support issues.

  https://servicedesk.agile-it-management.de/servicedesk/customer/portal/2

  Your help is really appreciated and we will respond immediately.

  Best regards,The AIM Team

Very useful plugin for every team using the agile workflow in jira! Fast overview and matching to resources

Thanks for this plugin. I already use your resource management plugin. It has helped to synchronize employee assignments with task scheduling and to have at a glance. thumbs up

{quote}4. Detect deviations from original estimates easily! {quote} Difference column is miscalculated. Here is my scenario: View Mode: Both Aggregation mode: By Task Name: XX-218 Issues: 5 (1 task + 4 subtask) Orig. estimate: 1w (1w in parent task, no original estimate in any subtask) Rem. Estimate: 3d 5h (1d 3h logged work in parent task) Logged work: 3d 6h 30m (logged work in parent task + subtasks) Difference: 2d 3h 30m According to my “common sense” to detect deviations from original estimates difference should be: Orig. Estimate: 1w – Logged work: 3d 6h 30m = 1d 1h 30m And AIM plugin says 2d 3h 30m what is not helpful at all.

• 

  AIM - Agile IT Management

  Dear Mr. Porcar Nadal,

  thanks for testing and evaluating our plugin! We would like to address the issues you raised:

  The difference column is calculated according to this formula as described here:

  difference = original estimate - remaining estimate - logged work

  This value is aimed at the case in which deviations from original estimates can occur if in any issue or sub-task remaining estimate plus logged work is higher / lower than the original estimate.

  It indicates deviations in total expected work to be done in a sprint or an issue,€“ i.e. œDetect deviations [of current estimation] from original estimates easily!

  This is a quite common requirement addressed by our customers we wanted to address in the first place.

  The approach you describe compares logged work against original estimate which can be derived by direct comparison of the values.

  But still the following solutions could be provided in upcoming releases:

  • We will add a hint in the popup how the current difference is calculated.
  • Your use case could be reflected by a configurable second option or a second column for original estimate, logged work.

  There is a JIRA Service Desk available for feature requests and other support issues. We would be glad to refine this requirement in detail there.

  If this features give you more added value and increase your rating we would be more than happy to add them.

  Best regards,

  The AIM Team