Comments
-
I am hoping to spend some time getting some ACE events set up here in Dubai. Especially hopefully about getting some Atlassians here in person for the events.
-
Hi Jill, I would contact Atlassian support about the question on whether the new functionality can be overridden. https://support.atlassian.com/contact/#/ They will also be able address your second question. Please post back here with their answer so we can update future readers here.
-
Hi Keith - Welcome to the Atlassian Community! There is a basic built-in form that comes with JSM. However, if you want something more robust, like conditional fields, you will need to install the ProForma app add-on - either paid or free.
-
Thanks @Monique vdB ! Looking forward to another great year!!
-
Hi Anzhai - Welcome to the Atlassian Community! Are the uncompleted issues sub-tasks? Or do they have open sub-tasks?
-
Board Settings > Quick Filters Create a quick filter called Hide Epics. The JQL will be: issuetype != Epic
-
Tania!! How are you doing? Did you get this resolved?
-
Hi Nicola, Let me see if I have this correct - a service request is create in JSM. Then a corresponding JSW issue is created and linked to the original request. Is that right so far? And if so, you want the Reporter of the request to see the linked JSW issue. Correct? And if so, what is the next thing you would to be able…
-
Hi Krishna, The completed issues in a Sprint must be in the far right hand column of your board, regardless of the the status type or name. Only issues in the very last column will be considered closed. Otherwise, they will carry over to the next Sprint.
-
Hi Mary, You can create your Request Types and map them to different Issue Types. Then create your custom field and add a different context for each Issue Type. Then in each context, you can have different values for the same custom field.
-
Hola Valerie, No puedes enviar un panel, pero puedes enviar los resultados del filtro que utiliza el tablero. Simplemente vaya al filtro del tablero, luego haga clic en Detalles y luego en Nueva suscripción en Suscripciones.
-
Hi Arunajyothi, Sorry, but I am not aware of another way to do this. Maybe the ScriptRunner Behaviours app would have this functionality, but certainly there is nothing out of the box.
-
Hi Michelle, What is not working for you in Scenario 1? And can you post a screenshot of your current Rule?
-
Hi Maru, No, you cannot change the types of fields in Jira. You will need to create a new field with the new type and migrate any data to the new field.
-
Hi Tanushree, You will need an add-on to connect issues across different Jira instances if you don't have that already.
-
Hi Lyn, In the Permission Scheme for the Project, add the Reporter to the Browse Projects permission.
-
Hi Jeremy, If you did this in separate tabs/windows, you will need to refresh your Rules page before you will see any new custom fields show up.
-
Hi Andrew, You can certainly use information from both projects to accomplish some things. What exactly are you wanting to do?
-
Hi Matthias, I am not aware of any mechanism for a user to be a Read-only Admin in Jira. Your best bet would be to use an Admin account and then capture the data and post in Confluence or in your internal environment somewhere with read only. You might take a look at the Revyz Configuration Manager app in the Marketplace.…
-
Hi Britt - Welcome to the Atlassian Community! You need to add a context for the Custom field to include the Jira Work Management project. This should make the field show up to be able to drag it to the form.
-
Hi Amin - Welcome to the Atlassian Community! If the value for Field B is indeed getting updated, then the rule should fire. If you try just updating Field B manually, does the rule fire? If so, be sure that that box is definitely checked and you have published it as such. Can you share a screenshot of that?
-
Hi Mattis, Just as a note also, the projects associated with a board are only based on the value of the Location field in the board. So if a board uses a filter that includes multiple projects, it will only be "associated" with a single project - the one in the Location field. You might want to take a look at an add-on…
-
Hi Laura, If you have set the fields as required in the Field Configuration, you will need to create separate Field Configurations for each issue type. That way you can have different required fields based on the issue type. Go to Settings > Issues > Field Configuration Schemes
-
Hi Fikri - Welcome to the Atlassian Community! You need to get a quote from Atlassian since you are on an annual subscription. https://support.atlassian.com/contact/#/
-
Hi Henk, You might trying doing a Search and using Sprint = [the name of your sprint] to see what issues show.
-
Hi Steven, What do you mean by you created a project and associated it with another project that were were creating on the fly? I don't think that is possible - the first project must be created and established first. Are you a Jira Administrator?
-
Hi Joanne - Welcome to the Atlassian Community! If it is your personal ID, try using your email address used by Jira. And or just the first part of your email address before the @ Also, can you post a screenshot of the actual error?
-
Okay, thanks for that. Let's step back and get some more info. Is it Team-managed or Company-managed? Assuming Company-managed, you are using a Scrum board but not using Sprints? Did I read that correctly in the other answer? Can you explain that more? Where are the issues showing? In the final column of the board? Just in…
-
Hi Alex - you might want to check out the Revyz Configuration App in the Marketplace for being able to clone a project, including the other items.
-
Hi - Just use the Approvers field for those who can approve the issue. You do not have to be an Agent to be in that field or to approve.