John Funk Community Champion

Hey @Chris Green - any update here? 

I don't know exactly how that works, but I would think that whenever your bill date is for the month is when the user will be counted or not. I am pretty sure it has nothing to do do with the number of active days for the month. 

Hi Menti - Welcome to the Atlassian Community! Can you provide more information please? 

Let me see if I can get someone from Atlassian to take a look. 

Great!

The user need to have Site Admin permissions to make that change. You can revoke on a daily basis, but you will need to do that manually for that one product. 

Hi @Per Flock - Did you ever get this solved? 

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

Hi @Arnav Yes, you can deactivate a user for just a single Atlassian product without affecting the other products. And it will indeed reduce the the license count. Navigate to the user at admin.atlassian.com and click off Jira Software under Access. 

Hi @Kate Aid - Welcome to the Atlassian Community! Blocked work is really whatever you define it to be. We define it as something that I want to work on but I physically can't because something is preventing me from making progress on it. Until that thing is removed, I can't work on it. We use the Flag feature to identify…

Not sure then. Maybe step through the process in this documentation: https://support.atlassian.com/confluence-cloud/docs/what-is-a-confluence-group/

Hi Glen, You can't currently do that with Team-managed projects. You can vote for that function and follow along here: https://jira.atlassian.com/browse/JSWCLOUD-17336

What are the steps you are actually doing and where is it failing? 

Hi Caroline, Make sure you are in the group. You have to be in it personally in order to place it somewhere else. Then you can remove yourself from the group. 

Hi @Didem Seda Taş I am not sure I completely follow your scenario, but see if this helps. Add a post function to the transition to the In Review status to set the Assignee to the Current User. When it goes to the Deploy status, it should still have the same Assignee if you don't clear it out, so it should be good. If you…

You could do that if you like, but it will change the key to the new project. For example, issue ABC-56 will become DEF-3 or something like that. You will still be able to see the history to know which project it came from. 

Hi Amit, I have not seen that message. I would go ahead and open a support ticket with Atlassian. https://support.atlassian.com/contact/#/ Please post the resolution back here. 

Was just going to write that up and @Bill Sheboy beat me to it. Thanks, Bill!

Hi Bruce, The best way to do that would be to create and Epic and link the tasks under the Epic. Then on the Epic, it would show you the percent done. 

Hi Mina, What is the difference between every edit and every time the date changes? If the data changes, that's an edit. Can you share a screen shot of your rule? 

You would have to hide the entire ticket from the user. You cannot just hide selected fields or selected sections. 

Hi Tomasz, Yes you can do this with automation for Jira. Here is some information to get you started. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get unlimited executions per month Automation Basics:…

Hi Douglas, I would create a filter that shows all of the issues in your project - something like: Project = ABC Save and share that with anyone that needs to see the data in the dashboard. Then create a dashboard and use the Issue Statistics gadget. Use Status for the Issue Statistic. That should get you want you need. 

Hi Paulina - Welcome to the Atlassian Community! No, it shouldn't affect them from seeing the linked ticket, assuming the projects use different permission schemes. 

Hi Bartosz, Check the Permission Scheme for your project. Remove him from the Work On Issues permission under the Time Tracking Permissions at the bottom of the permission scheme. 

Hi @Nawoda Herath - Are you still having a problem with this? 

Hi Sarah, Maybe add a format for the fix version date so that it is inline with the Due Date format: {{issue.fixversion.releaseDate.format("dd/MM/yyyy")}} Or whatever the Due Date format is. 

Hey Raju, If I remember right, you cannot create an issue from Microsoft Teams if you have a custom field that is mandatory in Jira. You cannot add the field in Teams. As a test, you can temporarily made that field not mandatory in Jira to see if it solves the problem. 

Vaya a Configuración > Problemas > Configuraciones de campo. Luego busque la Configuración de campo utilizada por su proyecto y haga clic en Configurar. Luego busque el campo personalizado. Finalmente, haga clic en Opcional para que cambie de Obligatorio a Opcional. Luego puede volver al campo y no seleccionar ninguna…

Por lo tanto, parece que necesita cambiar la configuración del campo para que el campo personalizado no sea obligatorio. Entonces debería poder no tener ninguna opción como predeterminada.