Comments
-
Ok, yes, you'll need to edit that "copy of" workflow and look at the transitions that go into "delivery uat" - it will have a "post function" on it that sets the resolution. Change it to set another resolution, or remove it completely to stop it setting a resolution.
-
Please do not mix up Status and resolution - they are two very different things. The resolution is set as part of the workflow. If you are using a simplified workflow, then look at the board configuration - there's a flag for each column. If you're not using the simplified workflow, then you'll need to edit the workflow…
-
Correct, the general principle is that your scrum person or team lead is in charge of your project and hence has project admin rights (including the control over board and sprints). If you trust your developers not to make a hash of the boards if you give them admin rights, then that's great, let them have admin. More…
-
It offers up the transition screen.
-
Bulk operation is definitely the right answer. First, write down what status is in the "done" column on the board, and then forget the board. Run a filter for the issues you want to update. At the top right, there should be a menu with bulk-edit on it. If you don't have that in the menu, then you do not have the global…
-
This is what it says on the tin - Jira doesn't have enough space for the index. Check the disk space, check that there's a lot of it for Jira to use, and check the quota for the user running Jira if you have it enabled. Generally, on a windows box, Jira will report "can't open file" if permissions are lacking, not disk…
-
You can re-import the list - if the lines have the current issue number in them, then the fields will be imported as changes. But you'll need to work out why they were ignored the first time. Scripts can do it, including groovy. Jelly is deprecated, so I'd avoid that, and the standard rule for SQL is "don't". Just don't…
-
What integration? The marketplace doesn't list anything, even for Server version, let alone Cloud, where there is a limited list of addons you can use.
-
Could be all sorts of things - versions of Jira, Java, your database, unusual configurations, etc. I'm afraid we can't really tell you much without more information. What does the log say too? Even if it's just sitting there writing nothing, that might trigger someone to say "I've seen that, have you looked at ...." I'd…
-
Best thing to do is import them as pages - https://confluence.atlassian.com/doc/import-a-word-document-into-confluence-170493136.html
-
There's a workflow property you add to steps where you want to stop edits. I can't do it from memory, but open up the JIra default workflow and look at the "closed" step's "properties". You'll find it is used there.
-
No. Your customers should not be in a position where you're giving them any access other than the portal, they should not have Agent rights at any time. You need to build the workflow so that the customer's feedback can trigger the right steps for Agents to monitor in the background.
-
You really don't want your project leads having admin rights, they can (and usually do) make a right mess of your Jira. Admins should be a very small group of people - 3 to 10 at most
-
I'm afraid it's not possible on Cloud at all. All the ways to pre-populate a summary rely on tricks that are not available to Cloud users.
-
Script Runner is not available on Cloud.
-
I'm not sure. I doubt the version of JIRA matters, but could you confirm it just on the off-chance? (unless you're on 1 or 2 - they had some really strange oddities in filter exports, but the lowest I've seen in the last 5 years is 3.0.3) I assume it's repeatable for that user, but does someone else exporting the same…
-
Atlassian don't delete the data at the end of the trial, it persists for a while (several months I think). Get a new licence and you'll get access to your data (Even if it's a new trial, rather than a purchase) I'd try nipping into your account and seeing if you have the option to extend the trial - that will get you…
-
I'm not a networking firewall expert, but it does look like that would block most incoming connections. Also, I thought you said it had been turned off? Could you try actually turning it off briefly to see if you can connect
-
No, it should have connected on port 8080, not 23 (23 is default for telnet) If your Jira is running and not firewalled by your network, it should respond to telnet on 8080 (it'll look rubbish, but that's fine, we're just interested in a response that returns data, or the error message explaining why not)
-
Then it's some firewall between your client computer (the browser) and the Jira server. When you say your firewall is off - you do mean on the Jira server? Could you tell us what happens if you try "Telnet <jira server> 8080"?
-
SO is Jira actually running? What do you get if you try to access it locally?
-
So what were the outcomes of all the debugging suggestions in this question?
-
No, the problem is your network, not Jira. The fact that you can get to it on localhost:8080 tells you that Jira is running, accepting incoming connections and responding to them correctly. I suspect your "open source product" is running on another port, one that your network is not blocking automatically. So you need to…
-
That's a networking question really - something on the server, or in your network is stopping access. Start by checking the firewall settings on the Jira server and all machines between it (proxies and routers). A lot of installations block most ports by default and need adjusting to allow services to be accessed.
-
Sorry for the delay.You're going to need to increase logging to find out what is looping here. Also, more detail, when you use "create space", what are the full symptoms?1. What type of space are you creating? A simple one? Or from blueprints?2. Define "infinite loop"? What do you think is looping? Do you mean "the page…
-
First, stop messing with the database. You should never touch a Confluence database while it is running, and you probably shouldn't touch it at all, unless you know exactly what you are doing. The loop you have in your log is about synchronising the list of users with Crowd, it has nothing to do with space creation. What…
-
No, there is no way to do this without a bit of coding. The short text fields are limited at about 250 characters (I apologise, I can't remember the exact number - I want to say 255, but I'm really not sure). You would need a field with a different entry template, or some ugly javascript hack to do this.
-
Very true, but Rahul has hit upon a better option than custom fields (I was heading to labels because they're flexible, but was thinking a bit too close to the search, and Rahul beat me to it)
-
Labels is a far better way to do it. It also gets around the problem that Christian mentions (the "changed" operator doesn't work for all fields), and it will leave you with an easy way to refer back to meetings later if you choose informative labels. Such as meeting_dd_mm_yyyy (just remember you can't use spaces in labels)
-
Use the "changed by" function, naming the attendees of the meeting. See https://confluence.atlassian.com/display/JIRA/Advanced+Searching for other functions you might find helpful