Comments
-
But start of day (2d) is useless to me in some projects. One size fails miserably to work for everyone. Even my PM and Consultants need different reminders to me, and we're all working on the same things in the same projects. If you had read the postings properly, you'd have seen the one that says "The difficulty with the…
-
On a dashboard, add a 2-dimensional gadget to do this. If you want it in any other format than a grid, you'll need to find or write a report or gadget to do it.
-
It does have reminders. It just needs you to define ones that work for you. Have another read of the conversations above and you'll see why it doesn't do "one size fits all" (because it's broadly useless), and your various options for getting them working well for you.
-
There is no issue. Lexorank is better than numbers for ranking, both for coding in Cloud and Server, and it's pretty much mandatory for data-centre. There's a good reason the original number system was dumped in favour of it, and numbers will never be re-implemented (they weren't great before as they couldn't be 1, 2, 3 in…
-
No, sorry, I mean the whole of your column setup - what have you got on that screen?
-
You can use "bulk edit" to do it in blocks (select a set of issues you want to move to a particular old type, then use "move issue" to change the type)
-
Go and have a look at the list of custom fields. You can hover a cursor over each "edit" in turn and look for the id in the tooltip link that appears, but it might be easier to read the raw html to find it. Or you could use REST to ask the create screen what fields are needed.
-
What does your board configuration say in the "columns" section?
-
Yes, it's not made it to Cloud yet. There's no way to do this at all on Cloud, you'll need an add-on to provide a post-function or listener to read your "severity" field and calculate a priority from it.
-
Actually, you almost can "just copy it". Stop Jira and make the copy. Make sure you retain (or recreate) all permissions and ownership when you copy. Go to the Jira installation and find /atlassian-jira/WEB-INF/classes/jira-application.properties - edit that and change the home directory line (it's likely to be the only…
-
We're not here to do your homework for you. Unless you have a question about the Atlassian stack that isn't covered by a read of https://confluence.atlassian.com/get-started-with-jira-software . I'd recommend reading up on basic development principles. Maybe starting at https://www.atlassian.com/agile ?
-
Cloud only uses <something>.atlassian.net for the service. If you want to change that, you have to buy a new <something>.atlassian.net, export the data from the old one and import it into the new one.
-
"None" is not an option. It is what Jira displays to the user when the field is empty, or to select "field is empty" when they want to clear it. That's why REST does not report anything - there's nothing really there! To "select" none, don't put anything in the field.
-
No. It's way too old. The docs recommend "latest version of Jira" and I would not try it with anything below 7.7 at the moment, as the last time I looked, Cloud could not import from 7.6
-
I suspect it's working, but adding 1278 milliseconds to the date is not changing it enough for Jira to display any difference.
-
It sounds like your import broke the database. I'm not sure why you are importing though, if you've done an upgrade the recommended, there's nothing to import. I suspect you need to go back to your 7.3 setup with the database you restored and then upgrade it via the recommended route - running the 7.8 installation and…
-
As per the doc, take an export of your 7.8 system and load it into your Cloud system. Database is irrelevant, the xml is independent of it. Cloud and Server are different licences, you'll need to pay for your Cloud system and then let your Server licence lapse.
-
First hit on any search - https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html
-
Same answer. You've amended a config file and made a mess of it. At a guess, I'd say it's the application properties file where you define confluence.home
-
You have not given us a log, and the error in your original question points to what I said already - an incorrectly formatted file.
-
Something in the config has been changed somewhere. Have a look through https://confluence.atlassian.com/confkb/confluence-does-not-start-due-to-spring-application-context-has-not-been-set-218278311.html
-
No. "Integrate" is a suitcase word - while we know it means "make two things work together", it could contain anything. So, we can't help you "integrate" beyond telling you "Yes, go ahead and do it", because you've told us absolutely nothing of any use in telling us what you want.
-
This error almost always means a configuration file is incorrectly formatted. Often server.xml, and it's almost always caused by a human editing the config files and mistyping something (although, if you're on a windows box, some editors do dumb things to text files that can corrupt them as well)
-
Yes, go to the request definition page to add fields. JSD does not do dependent fields natively, you'll need some code for that.
-
No. A project type is provided by the application that defines the type. Projects have a fixed set of characteristics and there's no functionality to add your own characteristics. You might want to have a look at the "pro fields" add-on though.
-
You could use the "priority scheme" functionality to do this if you're on the latest version of Jira.
-
No, there is no field type that will do this.
-
The multi-level-select list is not supported by Service Desk. This is a bit of an odd one. For a field to be selectable for Service Desk, the Service Desk code has to be able to support it. This is the opposite to Jira, which just needs an add-on to say "this is a custom field" (and then define how it works). JSD needs the…
-
Yes. Start by defining what you want from this "integration"
-
That article gives a list of the most of the reasons I'm afraid we can't help you with the error you have because 99% of the time, it's going to be caused by an item on that list. All we would do is take you through the same list of potential causes. The reason you are having it is likely to be because you've got something…