Hernan Halabi Community Champion

Hi @taelor toews in cases like this I usually setup one board per project and another board that contains all the projects that are linked to each other, it's all about the query you do to setup the board. On the big board I do setup the linked issues to be shown on the cards so I can see at glance which are the related…

You would have to update your board query to have something like this. I would it's going to look something like this Project = xxx and (issuetype != Subtask or (issuetype =subtask and status in (open, closed))) The other board should be Project = xxx and issuetype = Subtask So when a new Subtask is created team A will see…

From the images it looks like it did install but it's disabled, what happens when you try to enable it again? Do you get any errors?

I would review the white list on the other tools you might have, in case you need to update that info there as well

hi @Tom Horton unfortunately you can't do that 

Quick filters are meant to reduce the amount of issues you see on the board, they can only show things that the board already brings as a result of the query associated to it. I would suggest that you include all the results in the board query and build the filter the other way around, meaning that if you select the…

I'm going to guess that the problem you have is on the workflow associated to the issue type. Check the status properties of the workflow used by stories, you might find a config there that is causing this behavior.

I'm afraid you can't, some of them come by default and can't be changed

Correct, that is the case. If they are not in the edit screen, then you can just view them

Hi @Sneha Philip the resolution would be to edit the workflow and remove the post function that comes from server. Installing the add-on most likely won't fix this since even though you can do the same that you configured in server, most likely there will be a different way to set that up, therefore it will continue to fail

Most likely the e key failed because you were seeing the ticket from an agile board. The url you should see should be something like https://youcompany.atlassian.net/browse/SUM-3 Where SUM-3 is the issue key. If that's the case, then what you see on the screen is the view screen. As I stated, the view screen also works as…

Hi @[deleted] you need to go to the board settings and on the columns section, associate an status (the first one should be the right choice) to the backlog column, that will bring back the backlog to the board

Hola @Miguel Montalvo contáctanos por nuestra web Https://www.elite-it.me y de seguro podemos ayudarte, tenemos un equipo que trabaja a diario en esto. Saludos

Sorry but your can't do that. Request types are based per project and can't be shared across multiple projects.

What you are seeing when you open a ticket is the view screen, on it you will only see system fields and custom fields with values on it. Meaning that if the custom fields are null, those won't show up. Within the view screen you can edit fields as you describe (only this you set on the edit screen), but that's not the…

There is not such thing as you define it. You could add that as part of your project description or could be the date you start your first Sprint if you prefer, but there isn't a place in Jira where you define such thing

I would suggest to make a query and subscribe to it. The query would check on a daily basis what's scheduled for that day and would email you the list of tickets. Anyway, it you are working in Jira you can have that same query on a dashboard or agile board and you would just go there everyday to see what's on the list.…

I didn't setup data center, but I don't see why you couldn't. I've run Jira with MSSQL on a version that wasn't supposed to be supported, I have setup Jira on docker when it said it wasn't supported, I wouldn't expect any difference here. In the end Jira runs in Linux or Windows, doesn't care what's running behind that.

certainly you can... just some of the options I mentioned wouldn't work since slas are a JSD feature, yet there are addons to overcome that limitation as well as to automate workflow transitions.

You can show transitions to customers if you want. You need to edit the workflow, select the transition and choose to show it to costumers on the portal.

I have deployed Jira in GCP in the past without issues. Shouldn't hurt to give it a try from your end

We had this issue in the past, in our case the problem was in the way that confluence was creating the users. I can't recall the whole config but the environment was using active directory and confluence was bringing users from the AD instead of Jira, so the customer accounts never existed in Confluence which caused this…

If you have more than one project you will have this behavior since you can't pick the project in which you are creating the ticket from the agile board interface

I believe that with extension for Jira Service desk you can do that

Someone at some point will have to do something. Some alternatives you might have are: Use automation module so whenever anyone adds a comment, then the ticket moves to the next status Use SLAs to transition issues when the time expires. If the process happens in other tools, maybe you can develop something that updates…

I would start by checking if the workflow configuration doesn't have a mistake in those transitions, specially the validators part

I like EazyBI if you ask me, is very flexible when dealing with reports and if ever needed you can import information from other sources apart from Jira as well.

Hello @William Chen (Merchants) whoever you add as a customer will end in the service desk customer role. They are the same thing in the end and you don't pay for those users

Glad to hear so. Eventually someone is going to create a project the other way and you will be back into the same problem. You might want to document that very well, or as we did, developed a solution to create the projects based on other projects along some extra project configuration like groups and user management all…

Hi @Rocio_Mtz did that work?