John Funk Community Champion

Hi Bharani - Welcome to the Atlassian Community! If you just press Enter, it will create the new issue. Or you can clear out all of the text and press Enter to "cancel".

Hi Terry, There is no Trash for issues. There is a Delete, which is permanent. How did you move the User Story to Trash? 

Hi Colleen, Switching out the workflows will not case a problem to the existing workflows or affect any projects that are currently using the shared workflows. The major thing that will be affected are all of the issues on that single project that you are moving to the new workflow. In a nutshell, any issues that are in a…

Hi Vanessa, I don't think you are going to be able to tag an alias at all. What exactly are you trying to accomplish? 

Hi Seamus - Welcome to the Atlassian Community! Do you have any scrum boards in your instance at all? Or would this be the first one? I tied it in my free instance and projects show up. What type of project have you created that you are trying to attach it to? 

Hi Serge, I would suggest going to the Issue Layout screen and see if you have a better idea of what is going on there. See if the fields show up under the Client tab on that screen. 

Hi Vina - Welcome to the Atlassian Community! It is probably that the Due Date field is not on the Edit Screen or Edit/View screen for the project. If you add it there, you will then see the field. Go to Project Settings then click on Screens. Then click on the Edit/View screen and add the Due Date at the bottom of the…

Hi Nikole, Sometimes user emails get blacklisted by Atlassian during the signup. I would suggest you open a support time with them. https://support.atlassian.com/contact/#/

Happy to help!

The old projects are still there and you can create a project based on an existing project. And then you can combine that with automation to probably achieve what you want. 

But you said the assignee is getting updated when the Epic moves to In Progress. I would check there first. You can also check the transition to Done for Sub-tasks to see if there is some type of post function firing. Finally, look at the history to see the timing of when the assignee is getting set and who the user is who…

Hi Marcela, We tend to use Projects in Jira as teams or product lines as you mention. Then we use Epics to track more traditional "projects" within the product line or team. 

Hi Luke, It looks like the Field Configuration scheme attached to this project and issue type makes the the Component field mandatory/required. You will need to change the Field Configuration to not have the Component field mandatory or you will need to add some component values to your project and populate the field on…

Hi Maegan, No, you can't copy an email into the Reporter field - it will need to be the user account ID or will need to come from another User picker type field. 

Great! Glad that worked for you! Can you click on the Accept Answer button so we can close this out? Thanks!

So I am wondering if there is a post function on the transition to In Progress in the workflow..

I have to admit that I am not one for dares either. I would probably be a dare that I say a particular thing to somebody, but I can't remember an exact example. 

Oi celso, Você pode conectar o projeto ao Esquema de Tipo de Problema a partir das configurações do projeto.

Gotcha. Yeah, the Backlog thing is pretty much only going to work with Jira Software projects. You create a new board for the business project and use the Backlog with that. It just won't show up under the project. 

Very good - it is a Business type project :-) Can you share a screenshot of the rule that you have so far?

Hi Whitney - Welcome to the Atlassian Community! If that is working for you so far, try this: project = AZTB AND component = WMT AND (labels != Workflows or labels is empty) ORDER BY labels DESC, created DESC

Hi Josef, What if just put a condition on the transition so that only a limited group of people can see the transition. 

Hi Mike, Basically what I do in the situation is link the project to a permission scheme that is very limited as to who has permissions to Browse Project and Create Issue permissions in the scheme. 

Hi Binu - Welcome to the Atlassian Community! The user may have been backlisted by Atlassian during the signup process. Open a support ticket to have them check: https://support.atlassian.com/contact/#/

Hi Drishti, Create an Automation for Jira rule based on an Issue Created trigger. Then add an new action for Manage Watchers In the add watcher section, use {{issue.reporter}}

Hi @[deleted] - There is a free app for Automation for Jira called Lite and a fully functional paid one called Automation for Jira Pro. 

Hi Hakan - Welcome to the Atlassian Community! It looks like you only have the Jira Core product installed. Or you do not have permissions to create Jira Software projects. If you are a site-admin, got to admin.atlassian.net and see what products are available. 

I would go ahead and create a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Hi Marcos, No, all users needing access to see issues must have a license. The only way around this is to use Jira Service Management and add users as Customers which are free. But they would only be able to see the issues they create. 

Hi @Spiros P. - Yes, that is close, although the fields you can use with lookupIssues is limited and probably doesn't include the organization. But give it a try. You can see more here: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues