Comments
-
You'll need to start by explaining what SDFC is
-
You can't, without coding. A select list is a field who's content options are set by an administrator. You'd need to log in as an admin and add the new option. This is not a function available under REST, so the only way to do it externally would be to give Jenkins an admin account and do some scripting in the GUI. The…
-
Single-selects are already "stattable". The add-on you've got there is for making other fields do it too.
-
You probably don't want to do that, because hiding the column means you can't drag issues to done any more Two better options * Use Kanban as intended - click "release" regularly to push the done issues off the board (a couple of teams I know do it after their regular progress report meetings, as they can show people what…
-
You'll need to write your own classes and templates for a completely new form.
-
Have you got permission to see them? Check project permissions -> browse
-
Yes, just applying a 100 user licence will be enough. Paste in the new licence key and you're done. You don't need to worry about anything else here. (Downgrading licences, different story. Upgrade not an issue)
-
Ouch. Well, the *confluence* version isn't in there, but the confluence-data version is, and that is a very close matchTry the highest numbered line in table Confversion
-
It's not held in the database. Why do you ask?
-
It sounds like the user is not assigned any issues in the second project. What happens if you run a normal filter for "assignee = that-user and project in (projectA, projectB)"?
-
* I'm afraid not, Atlassian pretty much said "no more type-2 addons will be added to Cloud, everything is going to be Connect addons in the future" at Atlascamp. I don't know if Perimeter could be converted to a Connect addon. My instinct is that it can't, but it's been a while since I wrote any code, and there are many…
-
Not really, there's no scripting on Cloud instances of Jira. I suspect the best you can do is use a remote REST call to pull the results of a filter and then push the issues through your auto-archive transition.
-
You need to remove the users from any group that lets them log in. By default, this is the "jira users" group - could you check that group and make sure it has 10 or less users?
-
The fields you are working with are set to render as "plain text". Go into the project, look for "field configuration" and descend into that. Find the text field(s) that need to be more clever and look to the right for "renderer". Change it to "wiki renderer" and you'll find they display formatted text.
-
You are going to have to go over all the settings.Check that the field has the right context in the list of custom fieldsCheck that the field is not hidden in the field configuration scheme for the project/ and issue typeCheck that the field is on the screen for the project and issue type by going through the issue type…
-
Hide will never lose you any data - you have to physically delete the field to do that! Have you hidden the field in your own personal "show fields" settings by accident? Should be the option to the top right of the create/edit.
-
It's 125 users. However, if you need your agents to use software functions, you'll need to include them in the 100 Software.
-
Not forgetting to *read the logs* - they should tell you what is going wrong. Try atlassian-jira.log first and catalina.out if there is no jira log.
-
Go to the configuration of the board and select the restrictions you need. I'm afraid your question doesn't tell me anything about what you want or what you're trying to do, so the best I can do is say "go do it"
-
A different way to view and interact with your issues.
-
Ah, thanks Michael, I wasn't sure how much of it was just for OnDemand.
-
Start by upgrading to version 5.2 - after that, some of the rest of the "design" is OnDemand specific, so you're a bit stuck. Might be able to get closer with a bit of css amendments etc. But you'll need to be specific about which bits you now want.
-
Er, that sounds very wrong. You should stop the application, put your changes in and then restart it. Do you mean that all works the first time, but it reverts the next time you restart? Have you taken the plugin apart and rebuilt it correctly? Tried removing the old one completely and making sure there are no copies…
-
The advice on the issue you've raised seems correct to me - you need to pull apart the plugin, change the templates, rebuild it, reinstall it and restart Jira - did you do all of that?
-
Well, no, we are not support and you did not give us much to work with. You should have raised the support issue as soon as you could, and had a response in a few hours (not even my trivial support requests have gone more than 36 hours without an atlassian response, even if it was just "can we have logs". And server-down…
-
Raise a support request at support.atlassian.com And/or read your log files to see what has gone wrong.
-
You'll need to read the logs to find that error and look at the root cause of it. It's far too generic an error to diagnose off the first line presented to the users.
-
Are you using Cloud/OnDemand? If so, then OnDemand has a limited set of addons you can enable and you do that via your OnDemand account, not via the plugin manager. You can still use the marketplace to identify addons you can use. If you're using Server version, then you need to talk to your admin
-
Please explain what this has to do with Atlassian products, or we can't help you