Vishwas Expert

Hey @Celine Penaredondo I guess you are trying in automation ? did you try filter subscriptions option in Advanced issue Search option. Please check out this video https://www.youtube.com/watch?v=gIeje1Qk3kY Regards, Vishwas

Hey @John Pinnell Welcome to Atlassian Community !! Cloud to Cloud site migration is available now OOTB. Please check these instructions https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/ Regards, Vishwas

please check my rule. I haven't put the edit condition at the top. We need to put a JQL condition there. Then at last the edit action. Also add the field created to the screen of the project.

Hey @Loredana That's correct starter packs aren't supported. I see the query and results, if nothing is shown then you are not affected by the issue as mentioned in resolution kb. Yes do the XML backup once again when the prod site is not being used. sometimes XML backups get corrupted hence issues will arise. I would…

Hey @Pantham Akhil Automation rule is ready. Before doing this i created a field called "Issue Transitioned ?" with Yes and No as dropdown values and added the field to edit screen of the project. Try this and let me know in case of any issues. Regards, Vishwas

Can you send me a screenshot so that i can understand better. Also did you do git gc ? that was another method to fix.

Let me write the rule and send it

Hey @Allan Baltodano Welcome to Atlassian Community !! This issue might be due to a workflow configuration — mainly Validations and Post-functions in the Create Transition. Mainly due to validators or post functions configured via 3rd party apps. Please check them and see if there are any issues there & fix it. Check this…

@Vivek Bohra Hope issue is fixed and everything is fine. Please feel free to accept the answer to help the community !! Regards, Vishwas

Hey @Joe Dahl-Fisher Welcome to Atlassian Community !! Try running below command in git bash inside that repository folder. First one shows what happens to the repo before doing an actual command which is second one. git remote prune origin --dry-run git remote prune origin Let me know how it goes. Regards, Vishwas

Hey @Praveen Chitturi To add on to what Pramodh has mentioned. In Automation if you try to configure for 2 projects then it will be be "Multiple Projects" rule. Which can be configured only in "Global Automation". So only Jira admins can configure those. There isn't other way to achieve this you need to have jira admin…

Yes yes that's the option, it will mention all the details needs to be performed

Hey @Sushmitha Miro for confluence plugin will be available in Atlassian Marketplace, you have to search in find apps section in application for the plugin and install. Please check this link for details https://marketplace.atlassian.com/apps/1217530/miro-for-confluence?tab=installation&hosting=server Regards, Vishwas

Hey @drazorenov What version of Jira server you have ? this advanced searching was introduced in jira 7.9 https://confluence.atlassian.com/jirasoftware/jira-software-7-9-x-release-notes-946034808.html#JIRASoftware7.9.xreleasenotes-devinfo\ And there will be only one column "Development" which would show commit or PR or…

Hey @Angela Bowles No idea on that, since this forms are part of atlassian now. There might some update on it. Also I dont see any feature request in that thread. We may have to raise a suggestion in Atlassian portal.

Looks like you are on starter pack, hence it is redirecting to community support. This one select from schemepermissions how did you run ? can you send screenshot. I would also suggest you to once again do xml backup restore(same backup) on test and run re-index. see if that fixes the issue. Or else we may have to start…

Hey @Scott Federman No problem, don't disable the default. try the value i have suggested.

Hey @joan collantes Not able to see screenshot, please send once again.

@Wim Van der Schans Check this out, in your board issues are filtered based on epic. So in this dropdown you can select what you want to see.

Hey @Vivek Bohra Please feel free to upvote the answer.. Regards, Vishwas

Hey @Angela Bowles Welcome to Atlassian Community !! from this post we could see that it is might not be possible yet https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Is-there-a-way-to-move-the-attachment-field-in-proforma/qaq-p/1042142 Regards, Vishwas

Hey @joan collantes Welcome to Atlassian Community !! When you mean you cannot publish what error it says ? When workflow is created newly it will be in inactive status, you have to attach to a workflow scheme and an issuetype in a project. And coming to site vs org-admin in the new improved user management experience we…

Fantastic, like I mentioned previously it was filter issue. Thanks for sharing.

Hey @Loredana What DB is being used for Jira ? There is a kb on the error you are facing here https://confluence.atlassian.com/jirakb/unknown-error-or-nullpointerexception-when-creating-a-project-in-jira-server-849170381.html Also a solved answer here where it is mentioned with postgresql DB with other than public scheme…

Hey @Rajesh Ramankutty Try adding the same JQL which showed 186 issues to the board. From the screenshot above i could see that query was just picking project name. So create a new filter for that version and attach to board and see if that woks. i could be thinking of another thing is are there any EPICS that have been…

Hey @jaysonids Take a look at this thread https://community.atlassian.com/t5/Bitbucket-questions/Unable-to-access-Organization-Repos-using-App-Password/qaq-p/1927287#M77716 looks like while creating the app password the workspace and other basic permissions are missing. Regards, Vishwas

Hey @Mkurama When jira and confluence are integrated we can use Jira Macro to display the issues in confluence page, take a look on how to do that https://confluence.atlassian.com/doc/jira-issues-macro-139380.html Regards, Vishwas

Hey @Scott Federman You can disable the default summary thing and then try adding this in Edit Issue Action in your automation. Comp Change Request {{issue.employee name}} Regards, Vishwas

Multiselect is not required, just a select value is fine like yes or no kind of options. So for the first time the transition happens, set the custom field value to yes in the same automation in another action. Let me know in case of questions.

No problem !! 4:30 PM you can send an invite