Comments
-
Hi Artem, Agreed - I am tun into this several times. You will need to open a support ticket with Atlassian and get them to move it over immediately. You should go ahead and pay first though. Do not let them tell you that it will just move over at the end of the trial - tell them you need it moved immediately to get past…
-
Olá Luiz, Não há necessidade de gritar usando letras maiúsculas. Dito isso, o acesso a um quadro é determinado pelas permissões do filtro do quadro. Portanto, se alguém alterou essas permissões, isso pode ter bloqueado seu acesso ao quadro. Como alternativa, tente copiar o quadro e, em seguida, alterar o filtro usado por…
-
Great - glad to hear! And you are welcome!
-
Great- glad you got it all sorted!
-
Hey Antoine, It's best to create a support ticket for Atlassian for them to take a look. https://support.atlassian.com/contact/#/
-
Hey Antoine, You should probably create a support ticket for Atlassian for them to review and provide feedback. https://support.atlassian.com/contact/#/
-
Hi Jaydra - Welcome to the Atlassian Community! Make sure that your final status is mapped to the last column in the board. Only work items in the last column of the board (regardless of status) are considered Complete. If that is not the problem, check the workflow to be sure there are no rules on the transition to the…
-
Hi Aparna - Welcome to the Atlassian Community! First, it is rarely good to delete tickets. You should not provide that permission to anyone except Jira Admins in my opinion. You should add a new status to your workflow for Canceled or Aborted or Duplicate or something like that. But sure to add a rule in the transition to…
-
Hi Diptimayee, What are you trying to accomplish?
-
Hi Jacky, You have asked the question in the Jira group, but you have added a tag for Trello. Are you asking about a Trello board or a Jira board? And if it is Jira, is it Team-managed space or Company-managed space?
-
There is no need to redesign and create a second rule. This can be achieved by using Re-fetch actions.
-
Hi Shehrooz, Go to Space Settings then Customer Permissions. There you can make it Restricted and control who can see it.
-
Hi Jacob - make sure everyone involved is on the same Team. Then should should be able to see them. Or it might be a permission issue associated with it being a Free subscription.
-
Hi Herve, If you are a Jira Admin, you can go to Manage Projects (now Spaces) then click the 3 dots menu on the right. Choose Space Settings. There you can see in the Details who is the Space Owner. This is probably the person who created it.
-
Hi Jussi - I am marking Bill's answer as accepted. Let us know if you still have questions.
-
Hi Simon, Maybe do a couple (or 3!) Re-fetch actions in a row.
-
Oh - I was afraid it was a TMP. That's one of the reason I hate those types of projects. I don't know that you will be able to solve it with that type of project - they are very limited and not good in my opinion. Sorry.
-
My two cents is that it is COMPLETELY RIDICULOUS to allow multiple fields with the exact same name. You don't allow that with statuses, and it shouldn't be allowed with custom fields.
-
It shouldn't because those should be valid values. Can you post a screenshot of the field and the values? Also, what type of project is this? Team-managed? Company-managed?
-
Hi John, If you are populating the Parent field for the Epic at the time you are creating your ticket, then you should be able to do that easily enough. Create an automation rule based on a Work Item created trigger. Add any Conditions that are needed. Then add an action for Re-fetch Work item Then add an action for Edit…
-
Hi Ika - Welcome to the Atlassian Community! It looks like you might have adjusted the standard work type hierarchy. Is that the case? Can you verify that the hierarchy has not changed? Can you share a screenshot of the hierarchy here? What work type is the form connected with? And what is the work type of the parent for…
-
Hi Chris, Yes, many people are upset with all of the changes. But this is a user forum and while it might feel good to vent, you really need to address it to Atlassian personnel directly. Maybe create a support ticket or click the Give feedback link on the bottom left of most screens in Jira.
-
Hi Andrew - Is your question specifically about the field needing to be Yes? If so, be sure the case matches. You say they have to be "yes" in your question (lowercase) but you have Yes in your rule (uppercase).
-
Hi Lauren - Welcome to the Atlassian Community! Were you able to get this resolved?
-
Hi Carl, Use generic names for Workflow statuses. Put multiple statuses in a single column if you have several columns - but it is best to limit the number of columns you have. If you have too many, your process is too complicated. Implement WIP Limits on columns and discourage users from working on more than 2 cards/work…
-
Test Answer
-
Hey Antoine, You should probably create a support ticket for Atlassian for them to review and provide feedback. https://support.atlassian.com/contact/#/
-
O Holy Night And if you are looking for something fun - Blue Christmas by Porky Pig. You might want to listen to Elvis' version first to hear what the original sounds like. But the Porky Pig version has me belly laughing every time!
-
@Joshua Lai - Certainly as that was what it was originally designed for. And it should work for multiple Approvers. Give a try and let me know!
-
Hi Grace, You can approach a couple of different ways. You can create different Done category statuses like Canceled, Done, Complete, Aborted, etc. These are very handy for reporting purposes and even automation rules. And it gives you flexibility for transitions to them. And items like Canceled and Aborted would be Done…