Comments
-
Visual Composer is not an Atlassian product, I think you've landed in the wrong place. (Visual Composer uses Confluence for docs, but appears not to have put any "help me" links in them, so people click the Confluence "help me" and land here)
-
Sorry, I've completely misread this and typed completely the wrong things, several times. I meant 6.4.13 - you can reliably upgrade from 6.4.13 just as safely as the advised level of 6.4.14. You *might* be able to jump from your 6.4.8, but I can't quite recommend that - I'd test it a lot more than 6.4.13/14
-
>the question or fear is when changing my project type can I change it back to "service desk" and the "project" will work like before Yes, I answered that before. I'm really not sure what is going on now, as there's only snippets of information here, and not the stuff we probably need to see. I take it you have restarted…
-
Ok, yes, an admin can add fields, but you can't convert between types (the data is stored in different formats - imagine you had a field with "elephant" in it and you tried to change it to a number...). Yes, you should add your own field, a numeric one. I'm not sure which "preview" you mean, but almost all the screens will…
-
If you were not getting the due date on the initial screen edit, I suspect it was already on the screen - the option list has all fields already existing removed so you can't add them twice. I would rename your custom due date field (Call it something slightly different that does not change the meaning, like "Due date" or…
-
Yes, but also the configuration - you can give an issue type a "field configuration" that differes from other issue types in the same project (and, of course, across different projects). When I mess up fields, 75% of the time it's because I have associated the wrong field configuration, and 24% of the time, I've got the…
-
No change. But your description of an archive is one of the standard approaches already. Create a permission scheme called "Archived". Grant only "Browse project" permission to one role. Apply it to the projects you want archived. Remove all users (except maybe admins) from that one role.
-
There are a whole swathe of products you might use: * JIRA Core * JIRA Software (Core + Software Boards) * JIRA Service Desk (Core + SLAs, portals etc) * Confluence Each one of these is a separate licence (but not Server - you'd run JIRA Core + Service Desk + Software as one server and Confluence as another)
-
You can set it up so that a user is able to create an issue in a project but not see it. It does feel a little odd, but it can be useful.
-
It's default and mandatory - have you done both? (Both are at an issue level too, not project)
-
That "Estimate" field is a custom field your administrators have added, and defined as a select list. You need to get them to add a proper numeric field for Story Points or estimates.
-
It could be proxies or addressing. Two debugging things to try first: * Check the base url is correct, then go on to the server and use "sslpoke" to check that Confluence can resolve it's own url and connect to it. * Check the logs at the time the macro error appears - what do they say?
-
The add-ons might not exist because you have been messing with the file system. Hard to say without knowing exactly what you have been trying. However, it does sound like everything is runnning now. So yes, it is fine to change project types, and re-install Service Desk (via manage applications!) and change the project…
-
I don't think it's very clear myself, but I'm not sure how I would improve it!
-
Your filters should be fine, it's just your personal view that has been saved. Go to "search" and hit the "columns" menu. Select "my defaults" so you know you're looking at your personal settings, and you'll see "restore defaults" beneath it. Click that. Next, go back to your report filter, click "columns" again, but this…
-
I think you changed your default personal default columns, and not the saved filter's columns.
-
Could you give us the plain JQL for the two queries, rather than describe them? Also, can you tell us if you have more than one issue type called "Plugs" on your issue type list (globally, not the project)?
-
You're high enough in versions that you can use much the same process each time. You really do need to go from 6.4 to 6.13 before trying to go to 7. 6.4 is too low a version for the jump to 7 to work. (That said, it might, but I wouldn't bet on it) You should be able to stop JIRA, run the 6.13 installer and tell it…
-
So much has been written about JIRA, it's hard to say that there's any one page that nails that particular question well. I guess the answer Atlassian would want me to give is "Start at https://confluence.atlassian.com/get-started-with-jira-software/i-work-in-a-software-team-844502157.html "
-
Both, and boards and queues too. Some people like the "assigned to me" gadget in the dashboard, some like a simple saved filter (which they reuse on dashboards). Service Desk Agents often use the queues to find their issues (although that is more often to find the next request to deal with, not the currently assigned), and…
-
Remove it from the "edit" screen, and then place it only on workflow transition screens that the power users can use. (Not ideal , as it means lots of transitions in a workflow, but it's the best you can do without code)
-
No. It does not. He stated "single select". You've given the wrong thing.
-
No, you're not getting it. Your solution is wrong because it's for multi-selects (and happens to be clumsy for them). There's no "opinion" or "agree to differ" here, it's a straight, black-and-white fact that your solution is incorrect. Imagine a simple case - I go to buy a car, and I say "I want a red car, with a blue…
-
I'm not sure what the rules are on which it might display either!
-
But that does not answer the question. Ritesh asked about Kanoah, not XRay.
-
No, please re-read what I said properly. The OP wants a single select list. You've given them a multi-select. We don't have the full requirement for where the field should be mandatory, and a validator *might* be right, but we don't know that. So, the solution does not work and is not what the OP asked for.
-
The jira-config.properties file has to live in, um, jira-home (and hence it can't define the jira home) Try <jira-install>/atlassian-jira/WEB-INF/classes/jira-application.properties
-
Not quite, and the solution is wrong too. The reason it is wrong is that you've used the wrong type of field. A checkbox field is a a multi-select field with a different display. You should have used a radio-button, as those are the same as single-selects. Of course, if you swap to a radio button, you'll now find it gets…
-
If there are no application logs in <jira home>/logs, then the application is not even starting within Tomcat. Read the catalina.out to find out why.
-
What do you get when you visit localhost:8080, and what do the JIRA logs say is going wrong? (Look in jira-home/logs)