John Funk Community Champion

Hola Aramirez: ¡Bienvenido a la comunidad de Atlassian! Puede encontrar más información sobre las direcciones IP de Atlassian aquí: https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html?_ga=2.142583344.384262003.1577710229-1313086432.1576012938

Very good - let me know if you run into any problems setting that up. 

Ah, sorry - I read the original question wrong. Automation For Jira will perform actions when items are transitioned, but cannot actually prevent them from transitioning. However, ScriptRunner or JMWE (Jira Miscellaneous Workflow Extensions) should be able to do that. 

It's usually not a good idea to modify the simple workflows. That's problem the start of it. You should create a new one from scratch if there are going to be major changes from a simple workflow. Once you get the first one created (that isn't a simple workflow), then you can copy that one and use it for the base for…

Okay - thanks for the update. If you can click on the Accept answer button, we can close this one out. Sorry it didn't work out the way you wanted it do. 

Well, if the card always goes to Backlog on Create and the Backlog status is mapped to the Backlog, then the only way to get them to a new status is to transition the issue. You might could create a new first column on your Board and map the Backlog status to that column. But not sure that's what you really want. 

Hi @Hy - The best option would be to get an add-on like Jira Miscellaneous Workflow Extensions (JMWE) or Automation For Jira. Then it is very easy. Without the add-on, you can probably accomplish it, but it is somewhat messy. 1. Create a new Custom Field and then use the Update Issue Custom Field post function to put GA in…

You might could do that with two different filters and then have two different gadgets on the Dashboard - one for Previous Assignee and one for Present Assignee. Other than that, I don't think a single query is going to be able to show you want you want. 

Hi @Fiona Macelli - Were you able to answer Alex's questions? Are you still having problems? Did you try out Automation For Jira?

Also, is this Workflow still Inactive? And how big is the Workflow (how many Statuses). You might be better off just deleting the entire Workflow and starting over. Was this copied from an existing Workflow or was it created new from scratch?

Sorry for all of the questions - are all of the transitions that you cannot re-name on the same Workflow? Or does it happen on different Workflows?

Hi John - Welcome to the Atlassian Community! That's a very good question, and one that we debate each time we need to do it. We consider Projects in Jira to really be Teams. So, for us to create a new Project in Jira, the first question we ask is whether this is a new set of people working together? Or is is just a…

What version of Jira Cloud are you using? Do you have the full paid version or the Free one? Or some other version?

Not sure how much of the history gets saved in the moving of issues. AAB to ABB to ABC - I think the AAB is still going to show up in the history somewhere. But yes, if you delete the original project, you should be able to re-use the project code. 

Hi @bharath reddy - Welcome to the Atlassian Community! You can also do that with the Automation for Jira add-on. 

Sorry, but since there are already issues attached to the old project code, you are probably never going to be able to use it again. 😞

When you say duplicate fields do you mean there are two different fields with the same name? Or do you mean you have two fields that are capturing the same data?

Do you have any issues that were created under the original project code? If so, that’s probably the problem. You might try again now as as maybe the system needed to finish a re-index.

Hi @annette_greenhalgh - Can you give us some exact examples or some screenshots?

Hi @[deleted] - You will not be able to change the look and feel of the list of sub-tasks on the issue view itself. You could change the color on the board, but not in the issue view.

@sadia_sher_360factors - did this answer your question? If so, can you click the Accept answer button so we can close this out?

Hello Hy, No, you will not be able to do that with a single custom field in Jira. You could possibly get the information you want using multiple custom fields, possible with Cascading Type. 

Hi @GARY BORGES - Welcome to the Atlassian Community! You might could do that using an add-on like Automation For Jira or ScriptRunner. You can cause auto-transition of tickets based on particular actions that happen. 

Hi Ayesha - Welcome to the Atlassian Community! This might be the best place to submit a support request for payments: https://fin-ops.atlassian.net/servicedesk/customer/portal/3

Well, if your custom issue types are subtask type issue types, then they are going to show up there. The other option would be to make them regular issue type and connect via linked issues functionality. 

Maybe try to add him on another project and see what happens? Without support, that's going to be tough to track down. Might even try to add a new user and see if that one can be added. Then delete the old one. :-(

Hi @sadia_sher_360factors - can you provide a screenshot of what you are seeing and what is not right about it? 

Hi @Baris Kuytul - I think the closest you will be able to come to is to email the link to the Dashboard. You could email each of the underlying filters through the filter Subscription if you like as well - that's what we do. That won't work real well for several different gadget types though. How many gadgets are on the…

Yes, but was referring to the Edit User Filtering where it has All active users are allowed. Maybe change that to use one group (not project role which would relate to the People setting under Project Settings). See what the permission scheme has for Browse Project and for Assignable Users. The latter shouldn't apply but…

Why are you trying to use releaseDate? You might could use: "Release Version History" = latestReleasedVersion()