Comments
-
It's usually because you've inadvertently accepted the suggestion to subscribe to a topic (the design makes it very easy to do that by accident) Do these three things and Answers will only contact you about account related stuff (less than once a year generally): * Go to "topics" and make sure you remove the watch from all…
-
Check the configuration of the mail handlers and check the log file for errors (JIRA home /log/atlassian-jira.log) If you can't see anything obvious, head to "logging and profiling" and enable the incoming mail logging stuff, then go back to the logs directory for another look.
-
Right, so the logs tell you everything. Your expired licence absolutely will block an upgrade. You can only upgrade to a version of Confluence that was released before the end date on an expired licence.
-
As Eduardo said, we need the logs he described. All you've given us here is the output of the startup process, we need the logs that Tomcat and Confluence generate as they start (and fail)
-
You can't really. The only good way to upgrade a Confluence database is to upgrade Confluence, letting it do all the work for you. If your system is not running after an upgrade, you need to look at why - what does the log file say is incorrect? If it's "data is old and I can't upgrade it", then you'll need to roll-back to…
-
You might want to consider setting it in the defaults as well.
-
Yes. Including the database and all attachments.
-
Nope. The uploads are limited in size to prevent overloading the server, and you've also got a 25Gb limit on the total storage on the system too. You can't increase the upload size of files on Cloud.
-
You'll need to write a new implementation of it.
-
Version fields work off the list of versions in the project. To edit versions, use version management in the project admin section.
-
I'm really sorry, I forgot the other parts.1) Are the fields different in the field configurations in *any* way? Mandatory, you've already done, but shown/hidden is the other question? (Renderer doesn't matter)2) Could you check the custom field *contexts* too? Are they different for the project/issuetypes being moved…
-
It's definitely not "random". It's stopping you from breaking your data by validating what you are putting in. Check the field configuration schemes for the source and target project - you'll find that in most cases, your "random" fields are optional in the source, and mandatory in the target. That's the configuration side…
-
I'm guessing you tried the download from a windows machine - the website takes a guess at which version you might want from the OS the browser reports. If you scroll down a bit, you'll find a link to "All Jira download options" Note though - Jira is not (yet) packaged for any particular Unix variant, you just need the…
-
There's two parts to this. First, identifying the fields - there really is no sensible way to do this easily. You'll need to go to the list of custom fields and change the name of every environment field in there to something more identifiable - environment 1, environment 2, environment 3 etc. That change can be temporary…
-
Duplicate of https://answers.atlassian.com/questions/43097014
-
It will be being purged by something. You can configure the Tomcat that Confluence runs in to do it with a bit of fiddling, but it's usually done best by the operating system - logrotate is the most widely used tool on Unix machines.
-
I'd add it to the workflow.Using resolutions is not useful - if *any* resolution is set, then the issue is finished with, resolved, ended, done. If you're waiting for some form of feedback from a client or PM and you don't want to mark it as "resolved", then you cannot use the resolution field. Because putting it in there…
-
It depends on what you mean by changing it to "pending". Issue status is an indicator of where an issue is in the workflow. So, to have "pending" as a status, you need to include it as a step in your workflow, so you'll need to edit your workflows to include it. Or, you might simply mean that a status that exists already…
-
That's not a bug (although it is counter intuitive) Screens, field configurations, and field contexts are separate things. You have separated the screens out so screen-scheme X is for bugs and screen-scheme Y is for tasks. But I suspect you have only set up one field configuration, and in there, you've made the field…
-
>Sorry, I am not that familiar with JiRa and use the term which we are using No need to apologise, I was just trying to say that people use different words for the same things and it's worth bearing in mind when posting. Because I spend so much time with Jira, I often say "issue" and get a blank look before I have to…
-
I don't understand the question. What's a "ticket" here? Jira uses the word "issues" to say "something that needs attention", which is what most people mean by "ticket" (which is not the correct English usage, but hey, language evolves). In other words, when "something needs attention", you should already have a…
-
Um, that's pretty standard. Have a look at the documentation on Issue Types and Workflows. Jira ships with a handful of issue types already (bug, improvement, task, etc) and it's a doddle to add more. You can then tell it "use workflow A for issue type X, workflow B for type Y and workflow C for type Z". And vary that by…
-
That's a restricted function on Cloud, you can't disable it.
-
You haven't told us what error you're getting.
-
Which scripted field type are you using? I'm aware of three ways of doing it.Although, what you need is going to be something likeString[] pointlessresult = issue.getKey().split("-")return pointlessresult[2]
-
The code I could send you depends entirely on how you you want to implement it. As a field plugin? A derived field (I'd use the script runner for that)?I still don't understand the need for the number when it is already on-screen in front of you.
-
Mmm, sounds utterly pointless to me, when you've already got the number on-screen.Anyway, you can't do it on Cloud, you need code that would split the number out and duplicate it redundently on-screen. Although if it's invisible to the user, there's actually nothing to do because no-one will see it.
-
Argh, sorry, I completely misread that, it's not the CQ bug id.The question is actually "how do I duplicate the issue id into an edit screen" - that's actually quite hard, and utterly unnecessary - it's already being displayed about the edit box, at the start of your red arrow.So I'm a little confused as to what you are…
-
So you want to show the QC bug number in JIRA. How does the HP-ALM addon documentation suggest you do it?
-
Ye,s but you've not described it, explained what it is, pointed us to an addon, or how it's not telling you how to do it in the documentation.