Atlassian Jira Align Formerly AgileCraft vs Zendesk Support Suite

• Effective Sprint planning : Sprint planning can be done using Planning Poker in AgileCraft by clicking Team > Manage > Other > Estimation Games very effectively for distributed teams.
• Team Capacity Allocation Report: After tasks are created at team or program level, the report from AgileCraft cab be pulled and can be verified that no team member is under or over allocated. A report can be generated by navigating to Team > Manage > Assign Tasks.
• Effective Requirement trace-ability: To maintain requirements trace-ability follow the steps below:
• Upload test cases against the story/requirement. once uploaded test cases will be visible under that story
• Execute Test cases in AgileCraft and mark them as Pass/Fail based on the actual outcome
• Based on test results, The acceptance criterion's can be marked as “Pass” or “Fail” & if marked failed corresponding defect can be logged & can be attached with the story
• So against each story we can easily see whether all test cases been executed or not & which acceptance criterion's are failed & how many defects are in open or close state.
• Daily Scrum: In AgileCraft, the option to run a daily stand-up is available from Team > Manage > Daily Standups. Selecting the sprint number opens the daily stand-up meeting window in which each team member's tasks are visible and hours can be burned against them. Conduct Scrum meetings in AgileCraft, and burn each associate hour against the tasks created during the meeting. The burn-down chart can be generated & viewed during the stand-up to check whether the team is on track.

Read full review

• Zendesk makes it easy to see if a question/ticket has already been answered/updated (and to see who answered it).
• Zendesk makes it easy for users to indicate if they are available to respond or not.
• Zendesk also makes it easy to respond as you can respond within the software/system. A one-stop process!

Read full review

• The initial ticket creation screen lacks some important features, such as assigning "point values" (a measure of effort needed for the ticket).
• The browser needs to be manually refreshed to see new tickets, which can make things confusing when several people in a meeting are simultaneously creating tickets.
• The interface on some smaller portions of the software are sometimes difficult to understand.

Read full review

• Allow each user to customize the look of their Dash, rather than being hemmed in by company selections
• Provide a way for Suspended tickets (created by emails from non-users) to be better managed
• Set a timer for tickets to reopen on a more individual ticket basis.

Read full review

• It has a vast amount of features to implement in our project and the time management is a great ROI as well. As it is helping us to deliver our product in time.
• We can trace our sprint activity and it helps us to collaborate well.

Read full review

• The main part of the IT department is able to quickly prioritize and delegate tickets as they come in.
• Tickets can be linked to each other and support articles, creating opportunities for more efficient responses.
• Central location for users to ask for tech help when they don't need to know which staff member is the appropriate person to ask.

Read full review