6
45
Customers have installed this app in at least 45 active instances.

    AIM Agile Planning for Jira

    by AIM - Agile IT Managementfor Jira Server 8.0.0 - 8.13.0 and more versions
    Versions available for Jira Server 7.0.0 - 7.13.18
    Unsupported
    This app isn't formally supported.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    AIM - Agile IT Management supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Unsupported
    This app isn't formally supported.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Jira Service Desk
    This app is compatible with Jira Service Desk.

    Enhanced sprint planning and workload balancing based on flexible summation of estimates and logged work

    Enhanced sprint planning and workload balancing based on flexible summation of estimates and logged work

    Enhanced sprint planning and workload balancing based on flexible summation of estimates and logged work

    Sum up estimates for issues and / or sub-tasks!

    Switch between an issue and assignee based list!

    Sum up by column on Sprint and Kanban boards!

    Agile Planning is integrated on Jira Agile or Kanban boards. Different modes support summing up parent issues and / or subtasks in the way your team chooses. You can toggle through the modes directly on the popup.

    View original / remaining estimates and logged work aggregated by issues, assignees or status. Easily toggle between the aggregation modes on the popup.

    Keep an eye on sums of issues / sub-tasks during your Scrum or Kanban meetings. View original / remaining estimates and logged work aggregated by the columns of your Sprint or Kanban board.

    More details

    While supporting many agile projects and scrum teams regarding methods and tools we very often encountered a critical demand for enhanced information on the Jira Boards.

    Typically a development team needs to check the estimated workload for team members as well as stories (parent issues) basing on the work breakdown: original estimations, remaining estimations and logged work. But this is not easily done for two reasons: first of all Jira does not completely show sums of sub tasks and secondly there is no comparison on this level.

    1. Enhanced in place solution for sprint or Kanban workload planning!

    2. Sum up estimates for issues and / or sub-tasks!

    3. Switch between different aggregation modes: grouped by issues (e.g. user stories), assignees, status and columns of boards!

    4. Detect deviations from original estimates easily!

    If you are interested in a solution that compares the above mentioned with resource planning (assignments) you should visit our AIM Resource Management Plugin.

    Reviews for cloud

    (6)
    Sign in to write a review
    by Marcel Kaufmann on 2017-04-24
    Very useful plugin for every team using the agile workflow in jira! Fast overview and matching to resources
    Was this review helpful?YesNo
    by Robert Rudomski on 2017-04-20
    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
    Was this review helpful?YesNo
    by Josep PORCAR NADAL on 2016-11-10
    {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.
    Was this review helpful?YesNo
    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

    by Ben Richman on 2016-10-26
    Pro's: Good support, fast to respond (Had an issue where we had too many sprints and a patch was released quite quickly to rectify this) Negatives: No Summary field only ticket ref's (Hard to tell what tickets you're looking at) Cannot change order of tickets (Rank especially would be useful) Cannot change fields which appear within UI Drop down options on UI are unclear as to what they do In theory this would be a useful plugin but in all honest it would be better if it just put the rolled up estimates from the sub tasks+any estimate on the parent already onto the planning board card for that issue (The grey number on the right) rather than having its own UI to view the issues. This goes double when you cant change the fields you are viewing on the UI. Great support, poor plugin.
    Was this review helpful?YesNo
    AIM - Agile IT Management

    Thank you for your valuable feedback.

    Related to the issues you mentioned, the following entries are currently in progress and available with our next release:

    • The summary field is shown in the list of issues.
    • Issues are sorted by the rank (the order will be similar to the JIRA boards)
    • Context sensitive help texts are shown on the popup to clarify the selected options (our documentation here might provide some support in the meantime)

    We would be very interested in getting more details about "Cannot change fields which appear within UI". Which other fields would you like to sum up? There is a JIRA Service Desk available for feature requests and other support issues. We would be glad to discuss this request in detail there.

    Best regards,

    The AIM Team

    Update: The improvements listed above are available now in version 1.0.7!

    Reviews for server

    (6)
    Sign in to write a review
    by MeC on 2020-05-15
    Has a few bugs, especially on tasks with sub-tasks
    Was this review helpful?YesNo
    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

    by Marcel Kaufmann on 2017-04-24
    Very useful plugin for every team using the agile workflow in jira! Fast overview and matching to resources
    Was this review helpful?YesNo
    by Robert Rudomski on 2017-04-20
    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
    Was this review helpful?YesNo
    by Josep PORCAR NADAL on 2016-11-10
    {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.
    Was this review helpful?YesNo
    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

    by Ben Richman on 2016-10-26
    Pro's: Good support, fast to respond (Had an issue where we had too many sprints and a patch was released quite quickly to rectify this) Negatives: No Summary field only ticket ref's (Hard to tell what tickets you're looking at) Cannot change order of tickets (Rank especially would be useful) Cannot change fields which appear within UI Drop down options on UI are unclear as to what they do In theory this would be a useful plugin but in all honest it would be better if it just put the rolled up estimates from the sub tasks+any estimate on the parent already onto the planning board card for that issue (The grey number on the right) rather than having its own UI to view the issues. This goes double when you cant change the fields you are viewing on the UI. Great support, poor plugin.
    Was this review helpful?YesNo
    AIM - Agile IT Management

    Thank you for your valuable feedback.

    Related to the issues you mentioned, the following entries are currently in progress and available with our next release:

    • The summary field is shown in the list of issues.
    • Issues are sorted by the rank (the order will be similar to the JIRA boards)
    • Context sensitive help texts are shown on the popup to clarify the selected options (our documentation here might provide some support in the meantime)

    We would be very interested in getting more details about "Cannot change fields which appear within UI". Which other fields would you like to sum up? There is a JIRA Service Desk available for feature requests and other support issues. We would be glad to discuss this request in detail there.

    Best regards,

    The AIM Team

    Update: The improvements listed above are available now in version 1.0.7!

    Reviews for Data Center

    (6)
    Sign in to write a review
    by Marcel Kaufmann on 2017-04-24
    Very useful plugin for every team using the agile workflow in jira! Fast overview and matching to resources
    Was this review helpful?YesNo
    by Robert Rudomski on 2017-04-20
    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
    Was this review helpful?YesNo
    by Josep PORCAR NADAL on 2016-11-10
    {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.
    Was this review helpful?YesNo
    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

    by Ben Richman on 2016-10-26
    Pro's: Good support, fast to respond (Had an issue where we had too many sprints and a patch was released quite quickly to rectify this) Negatives: No Summary field only ticket ref's (Hard to tell what tickets you're looking at) Cannot change order of tickets (Rank especially would be useful) Cannot change fields which appear within UI Drop down options on UI are unclear as to what they do In theory this would be a useful plugin but in all honest it would be better if it just put the rolled up estimates from the sub tasks+any estimate on the parent already onto the planning board card for that issue (The grey number on the right) rather than having its own UI to view the issues. This goes double when you cant change the fields you are viewing on the UI. Great support, poor plugin.
    Was this review helpful?YesNo
    AIM - Agile IT Management

    Thank you for your valuable feedback.

    Related to the issues you mentioned, the following entries are currently in progress and available with our next release:

    • The summary field is shown in the list of issues.
    • Issues are sorted by the rank (the order will be similar to the JIRA boards)
    • Context sensitive help texts are shown on the popup to clarify the selected options (our documentation here might provide some support in the meantime)

    We would be very interested in getting more details about "Cannot change fields which appear within UI". Which other fields would you like to sum up? There is a JIRA Service Desk available for feature requests and other support issues. We would be glad to discuss this request in detail there.

    Best regards,

    The AIM Team

    Update: The improvements listed above are available now in version 1.0.7!

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$1025 users$10050 users$175100 users$250250 users$400500 & upAdditional pricing details

    Pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

    Can I install this app in a Data Center product?

    This app does not have a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.

    However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.

    Learn more about Data Center licensing

    Do you offer academic, community, or open-source licenses for server apps?

    For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are available for server apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.

    How can I buy apps for my legacy Jira Server or Confluence Server license?

    If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    AIM - Agile IT Management provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 1.2.10 • Jira Server 8.0.0 - 8.13.0 • Released 2019-11-05

    Summary

    Added configurable customfield aggregation modes

    Details

    - Added configurable customfield aggregation modes- Performance optimizations

    Installation

    1. Log into your Jira instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate AIM Agile Planning for Jira via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for AIM Agile Planning for Jira. You're prompted to log into MyAtlassian. AIM Agile Planning for Jira begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.

    To find older AIM Agile Planning for Jira versions compatible with your instance, you can look through our version history page.

    Similar apps