Comments
-
I'm afraid Trello is only recording what has happened. There are three broad possibilities here: * You moved the card * Someone else using your account moved the card * A computer moved the card, with an automation either within Trello or an external system. It used your credentials to do it, or it had admin access at a…
-
No, Jira doesn't have "skins"
-
First hit on every search engine - https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
1. To create new status, you need to be * An admin (edit the workflow to add status) * On a board where an admin has "simplified" the workflow (board -> columns -> add status) * On a recent version of Jira Server (7.5+ if memory serves) and with project admin permission to change the workflow 2. If you can't move something…
-
Yes, try https://marketplace.atlassian.com/plugins/com.refinedwiki.jira.servicedesk.refinedtheme/server/overview
-
You will need to explain "integrate" more. What does the user see when you "integrate"?
-
It cannot be the same, there is some difference between the users somewhere (other than name, password and email, which won't affect performance). You'll need to find it, then test what differences slows that one user.
-
You'll need to explain what add-on you are using to provide "in grid()"
-
No, because it's irrelevant where the issues came from.
-
Ah, right, that's a bit of a complex one to explain. It is easier to put it this way: * Go into each project that is using a scheme with a workflow you want to get rid of, and migrate it to a new scheme that you want to use from now on * Delete all the inactive workflow schemes * Delete any inactive workflows
-
Go into each workflow scheme that uses the workflow and un-assign it.
-
I was a bit over-grumpy on that one! Now it's deleted, you can ignore what I said in response! Thanks @RNV
-
What is different about this user? If they have an identical profile to someone who works fast, then the issue is not with Jira, but you have ruled most things out already, so we have to look at the difference. Find a similar user who does not have a speed issue and look at their account. Make the "slow" user absolutely…
-
"Customer request" is not an explanation of why you think you want to do this. It does not matter who is asking, the question is why? To get results faster, look at performance. Remove macros from the page, optimise the code for the macros if they're your code, get faster networks, make sure your users are using proper…
-
Are your users using plain text or the link option? How have you customised the link option to understand the new non-standard protocol?
-
I am sorry, but I do not understand the question. Most of it makes sense, but I am stuck on: >I can drag issues up and down but the rank doesn't updates. If issues land where you put them, then the rank does update. You could not possibly see a change if it did not. If they are not doing that, they jump back to where they…
-
Mostly right, but try flipping the "time tracking" off "none"
-
There are a few reasons this can happen, but I am not going to write an essay on it here, as it's long, boring and utterly pointless. Could you try looking properly instead? Use the internal java api or external REST api to look at what you want (SQL is the worst possible way to look at Jira data, please don't use it)
-
Hmm, I've got one nagging doubt left before I give in and go to Atlssian support and digging through logs. Could you show us the user?
-
Why do you think you need to do this?
-
Thank you Teri! At least I know now.
-
Try upgrading Confluence?
-
That would make absolutely no sense. The issue type defines what an issue is for, and hence is the definition of how it works. To change the workflow, you need to associate a different issue type with a new workflow and then change the issue's type to the new one.
-
Not by yourself. You need Atlassian to change something on the back end. I don't know if they will do it, but I'd really like to know if they will. Could you raise the support request to ask if they will do it for you, and let us know how you get on? We'd owe you for finding out!
-
It's not entirely fair - the last time I wrote a Connect add-on, you could not actually do "custom field" with them. But it has been a while (at least 4 years!). The "Connect add-on" is still right, just not sure about custom fields with Connect.
-
I suspect Shawn is slightly confused - this is a Service Desk Request field question, not one about Jira custom fields. To get a request to have fields, you do first need to have those fields available in the Jira issue, so his answer is partly right, but after adding them to the issue, you'll need to configure the request…
-
What does the issue history say for the assignee change?
-
Do you mean you want to: * Enter data on fields as you create? (Click on the fields offered, although you may need to get an admin to add them to the create screen) * Change the mandatory flags? (Get an admin to change the field configuration scheme)
-
Issue updated is probably best thought of as a catch-all for any event that is not something else. Comment, work logged, moved, created, <transition event>, and so-on, these are all specific events. Issue updated was originally for just "issue edited" effectively, but since Jira 2 has been used to catch anything else for…
-
I completely understand that. But plain Jira is not that interested at a project level, it's aimed at getting things done. I still would take a look at the profields add-on, but if projects are that important, you may want to have a look at Portfolio too. It won't add a lot to projects directly, but for your planning…