Blog post

Atlassian Answers

Home    —    Blog    —    Atlassian Answers
Aleks Yenin
Posted by Aleks Yenin
July 23, 2015

Atlassian answers

Question: How can I migrate Jira from OnDemand to new OnDemand?

Answer:
If you need to keep data in old JIRA simply follow this tutorial: https://confluence.atlassian.com/display/ONDEMANDKB/How+to+Merge+Two+JIRA+OnDemand+Instances

However, you need to use intermediate standalone JIRA to solve all the conflicts of merge – and then migrate the result to target OnDemand.

Question: I need to do a back up on a Confluence 5.1.2. I go to Backup & Restore–> Uncheck Back up attachments –> Click BackUp, but the page is sitting and just spinning its wheels. When I tail the log file not much really shows up. Just a routine Confluence chatter.

Answer:

 

Question: How can I get the issues that stay on one specified status for too long, like stay on “Open” status over 7 days or stay on “Review” status over 2 days?

Answer:  
Use JQL like:
status = “Open” and NOT status CHANGED AFTER “-7d”
status = “Review” and NOT status CHANGED AFTER “-2d”

 

Question: How can I allow customers access only their issues while allowing our employees access all issues?

Answer:

  • You should put your customer inside one new group, and remove that group from any permission scheme but the permission scheme of needed project. Inside that scheme, you should grant create permission to your customer group. Remove the customer from all other groups (now he cannot login into system)
  • Add this customer group into use JIRA global permissions: see https://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions
  • Add reporter to browse project permission into permission scheme of target project.

If you do those 3 steps – you will have 1 customer, one group called customers, a customer will be able to login to JIRA, see the list of projects without issues, create issues inside projects and see own issues.

 

Question: How can I move one particular issue to another project?

Answer:
If the history is not important I recommend to clone the issue, delete it after cloning,  and move the cloned one then. If you need to keep the issue – easiest way is to contact Atlassian support. Of course, you can delete an SQL record with duplicated idx_old_issue_key and try to move again, but result is not guaranteed. And don’t forget to make backups before such operations.

If this issue has key tag-15, then it seems you have tried to move the issue previously without success. There could be a set of partial results of unsuccessful movement and you should clean up them before next try.

Hope this small digest was useful for you!

Other services by Polontech

Services
Atlassian Migration Service-img-1

Atlassian migration

To Server. To Cloud. To Data Center. Server to Server. Cloud to Cloud. To Atlassian.
go to page
Services
Atlassian Products Configuration Service-img-1

Atlassian configuration

Jira Software. Confluence. Jira Service Desk. Atlassian addons. Custom scripting.
go to page
Services
Agile Training-img-1

Training

Fast start. Agile. ITSM. Atlassian.
go to page
Services
Atlassian Support Service-img-1

Support

Technical support 24/7. Health check. Upgrade. Data protection. Managed Services.
go to page
Services
Atlassian Installation Service-img-1

Installation

Choosing Atlassian products. Atlassian product at your service. Installing Atlassian in the cloud or server...
go to page
Services
Agile Consulting Service-img-1

Consulting

Audit. Jira Add-ons. Agile. ITIL/ITSM. User management. Team collaboration. Asset management...
go to page
Services
Cloud Migration Service-img-1

Hosting

Migration to Atlassian Cloud. Private cloud. Public cloud.
go to page
Services
Agile Portfolio Management Service-img-1

Portfolio management

Audit. Design. Launch. Support.
go to page
Services
Atlassian Products Licensing Services-img-1

Licensing

Buying. Renewal. Managed licenses.
go to page
Services
CI/CD Devops-img-1

CI/CD + DevOps

DevOps strategy. Commit. Build. Test. Deploy.
go to page

Use form to contact us