Comments
-
Hi Cristina-Elena, Pretty much only the shared schemes are copied over. Components, Versions, project description, people/project roles will still need to be created for the new project.
-
No, you will not be able to do that. Team-managed projects are completely independent.
-
That's probably why those fields are getting set then. You can check the history of the issue to see who/what is setting them.
-
Hey Ann - these appears to be the information you need. Let us know if it is not.
-
Hi Sweta - Welcome to the Atlassian Community! If I am understanding you correctly, you can create an Automation rule that triggers on when the Description field is updated and then send you an email.
-
Hi Ashok, When you say this is available with JSM, but you want to use with Jira Cloud - are you not using JWM in the Cloud version? Because that functionality is there, also.
-
@Siva Kumar - I assume you got this figured out?
-
Are you using a Roadmap with the project also?
-
Welcome, Jonathan! We are glad you found your way over here. :-)
-
Same with custom field IDs. They aren't going to match up.
-
That depends on what you mean by "configuration changes". If you mean that you change the shared scheme on one project will it automatically be changed on the other project? If that's the question, then yes it will.
-
WOOOHOOO!!! Nice job @Brant Schroeder !!!
-
Hi Alejandra - Welcome to the Atlassian Community! What message or error are you getting?
-
Hi @Valeria Faraone - Did you ever get this solved?
-
Hi Jaime, Yes, you can do that by setting up issue level security. Here is more guidance on how to do that: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
-
Hi Sreenadh, It will create the project using the same Schemes used by the existing project. It other words the two projects will share the Workflow Scheme, Issue Type Scheme, etc. But it will not create the same project roles or copy the people from the existing project to the new project - basically, just the schemes.
-
@Vish Reddy {Revyz} - Any thoughts?
-
Hi Johannes, Maybe send a link to the filter to the users to see if they can actually execute the filter directly.
-
What Nic said :-)
-
Thanks @John McKiernan as always!!
-
Hey Simas, Take a look at this article I wrote earlier this year. Please give it a like if you find it helpful. https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862
-
Hey @John McKiernan - Thanks for posting! Can we create the Creators now? Or do we need to wait until GA? If and now, what is that process? And how is someone labeled a Contributor? Are all of those just Project Roles?
-
Hi @editor1 Shell - Did you ever get this figured out?
-
Hi @Fred Stam - I don't see where you ever responded to this. Did you get it solved?
-
Glad you found it! Sorry we couldn't get to you before then. ;-)
-
Hi Ryan, What type of project are you using? Are you sure the users have access (i.e. it is shared) to the Board Filter? Can they run the filter outside of the board? What do they see when they try to access the board?
-
What is your exact scenario that you are doing? What type of project is it? Where are you creating the task?
-
Hi Gülsah - Welcome to the Atlassian Community! That's not possible with Jira Cloud out of the box. If you are creating a Form for the Portal, then you can do that, but not in a Jira screen. Something like this might be possible with the ScriptRunner Behaviours app for Cloud which is currently in Beta.
-
There might be a plug in out there somewhere, but having the ease of connecting a KB to a support request is one of the features of JSM. I doubt they will be adding that functionality to other Jira products outside of Project Pages. But I don't speak for them. :-)
-
Hi @Ivan Andrieiev Can you provide some additional clarity? Maybe some screenshots?