EddieW_h8oivr Expert

I undertsand your interest int he products, and the desire for feedback, but I do not feel this is the approprioate platform. If you want positive reviews, Atlassian's product site has testimonials and case studies. If you want the negative side just google the product name and "bad", "poor", or "failed".

We recommend that you do not use capability labels with space characters, if you wish to use them as variables. A possible solution for space characters is to format them with '${}' symbols, however, this does not work in all cases.…

Based on the docs I don't think that is possible. Once expanded it will stay so unil the page is reloaded. If selected, the code macro's content will be collapsed upon visiting or refreshing the Confluence page. Clicking the expand source link allows you to view this content. If false, the code macro's content is always…

To automatically manage agents I would suggest a free and open plugin I recently released that includes both json and bash-like output for easy automation. Use of security tokens keeps sensitive credentials out of scripts. https://eddiewebb.atlassian.net/wiki/display/AAFB/Remote+Agent+Management+with+monit

It is supported by Jamie's Script-Runner plugin's JQL aggregate functions, https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-AggregateExpressions But he suggests using the built in pie charts based on a filter for a nicer visual appeal.

Hey @todor I'm not sure if you were able to make progress, but I see you upvoted my answer ( a good sign ?) If you're satisified be sure to mark the answer "correct" so other users looking for unanswered questions can help other users.

Sorting the results can be done with a Lucene Booster, https://developer.atlassian.com/display/CONFDEV/Lucene+Boosting+Strategy+Module You can also use the Extractor module to enhance page's searchable indexes. https://developer.atlassian.com/display/CONFDEV/Extractor+Modulewhich will let you update/insert the indexes…

The "Responsibility" is based on * Last Committers * Manual Assignment (ad-hoc) * System Defaults The last one seems to be your issue, but If _you_ are committing to the repo, your name should override. Anyway you can have a server admin check this setting from the admin area: Add-Ons > Build Responsibilities And clear the…

Clarified my answer regarding #3. I was calling out Issue types (the umbrella concept in JIRA) not story types. ANd I think we are saying the same thing for #4 from different sides.

Your understanding is good, and they do have some great documentation on the matter. For Agile focused terms you will want to focus on the JIRA Agile docs (formerly greenhopper), for more general project/issue types you will use JIRA (core) documentation. #1 a place to hold _issues_ which may or may not be stories (see #3)…

We had an issue with our version of mantis being very...very old, and customized. We also will need to migrate close to 100,000 issues. So we actually wrote a simple php page (just modified the default report page from mantis) that filters the project/dates we are migtrating and generates a JSON payload. YOu can use the…

Make sure to enter the URL as https://mycompany.atlassian.net Also the basics: * Assumming you are licensed for both JIRA and Bonfire * You can view the site from the same browser/pc you are using bonfire

Tempo is not an Atlassian product, have you checked with the vendor's documentation? https://studio.plugins.atlassian.com/wiki/display/JTMPO/JIRA+Tempo http://studio.plugins.atlassian.com/browse/JTMPO

Any bugs found whilst testing are logging in JIRA and flagged as blocking the story. This allows us to keep track of the issues found and then resolved. That's my point. It's not a defect/bug at that point, its just an unfinished story. Bugs occur _after_ the story has been released to users.…

There is not a specific permission based on issue type, only the general "schedule" issues permission that allows them to be added to sprints. But addressing bugs in the manner you suggests sounds more like a Kanban board, OR stories being closed out prematurely (not properly tested)

Hi Kevin, i think you may want/need to write your own custom mail handler. This class can be copied from Atlassian;s existing examples, and modified to save the senders email in a custom field. https://developer.atlassian.com/display/JIRADEV/Custom+Message+%28Mail%29+Handler+for+JIRA…

hOW ABOUT something like rest/greenhopper/1.0/rapid/charts/scopechangeburndownchart?rapidViewId=1&sprintId=1 or /rest/greenhopper/1.0/rapid/charts/sprintreport?rapidViewId=1&sprintId=2

I would roll back the change. Use Field Configuration Schemes to create a "Versions are Required" scheme that project and issue type combos can elect into without affecting the entire population. There are a rnage of use cases where version makes no sense, especially Affects Version (anything not a bug!) Forcing fields…

No automated manner, but assuming all the tasks have been estimated you can just use multiple markers on the planning board, and assign each one the max velocity you feel your team can meet based on history. As one sprint is completed the next marker will be waiting and ready to start. BUt this is not really Agile/Scrum,…

Your comment is misleading. Major and minor have nothing to do with potential database impacts. Upgrade tasks can be bundled in any release.

In general Atlassian suggests migrations should occur on the same OS, but may include compatible upgrades. The filesystem depends on the OS, and even minor versions will include DB upgrade tasks. https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server…

The idea supports a Build-once-run-anywhere mentality. Build plans are for building and creating the release package/artifacts. * checkout from soruce * compile * test * package * ship to artifact server The build plan is linked with a deployment project, and exposes an artifact (war, ear, pom, etc). The deployment…

You can grant anonymous access to the space, and just apply a "Restriction" to the other top-level pages. (FAQ and HOW-TO must be top-level, without restrictions) The restrictions are inhertied by any child pages, and so applying at the top will ensure all content is locked.…

You _may_ be able to submit a support ticket and ask them to raise the count of the property to a higher number, but for performance reasons they may not allow it. https://confluence.atlassian.com/display/TEAMCAL/Recognised+System+Properties

Yes, I think the simplest solution would be a common triage pattern. Tickets with a type of bug, and a status of open has 2 workflow options {"start internal resolution","extenernal"} then, those new stages { "In Porgress - Internal", "In Progress - External" } in turn have their unique transitions, until at some point…

Check your config for the board.No sub-tasks should show in the planning view. They will show in the work view however (how else does the team know what to run with) See similar quiestion https://answers.atlassian.com/questions/108172/planning-sprint-in-greenhopper-6-with-scrum-board-no-subtasks-shown

Looks like they've yet to publish that info, https://confluence.atlassian.com/display/QUESTIONS/Votes+and+Expertsso I created ticket in their public issue tracker. I suggest you vote for it their, and provide any additional feedback as well. https://jira.atlassian.com/browse/CQ-640

Are you using Maven, or the packaged atlas-mvn (or did youalter the path to the settings.xml?). I have seen similar errors when using my default maven install which does not include the Atlassian M2-Proxy repositories. YOU would see download warnings above the snippet you shared if this is the case.

There is no direct migration from quickbase. But JIRA can import CSV and JSON to support migration from any other source. If you export quickbase to a csv file, you will just need to have the Attachment URLs in thier own column. JSON is a more powerful/verbose format, but may be trickier to get quickbase into that format.…

If you want the field to change without a workflow transition or client side JS, using Event listeners is the only remaining option I can think of. https://confluence.atlassian.com/display/JIRA/Listeners You can configure it to listen for the Issue Updated event and take whatever action you wanrt. You may not be able to…