Comments
-
Ah, yes, you do need to be a JIRA or System admin to edit screens.
-
That looks like a password field from an add-on. The one I'm thinking of blocks transitions (and may do work logs too) unless a password is filled correctly in the field on the issue. But I don't think it's available for recent versions of JIRA. Could you check what type of field customfield_10600 is? Go to…
-
It sounds like the component field is not on the issue "edit" screen. Go to the project admin and drill down through the "issue type screen scheme"
-
There's the error - it cannot connect to your database. Generally, you wouldn't connect "root", it's better to use a dedicated database user (so a database called "jira" with access via a user called "jira" for example)
-
That's why I asked about the issue type, as sub-tasks will appear on boards (assuming the filter does not exclude them)
-
Absolutely, both to the security level change via script, and "torturous". The scripting itself isn't too hard, assuming you've got a scripting add-on, but there's a couple of problems, in that 1. They won't stop "create" 2. The Epics will be invisible to all the other users, which kind of defeats the purpose of having them
-
I can't remember if wiki markup works in that field. HTML should though - try a <div> maybe?
-
The permission scheme for the project determines who can log work on issues in it. Assignee is one of the dynamic roles you can use.
-
No. The point of the Service Desk is that it keeps things simple for the customer and doesn't expose your internal processes or data to them. The intention is that your agents should be updating your users with appropriate updates, and if you want the customers to see the internal processes, then they should be JIRA users,…
-
Correct. There are some torturous things you can do to make it more difficult (clunky validators in workflows, and javascript hacks to change UI interactions for example), but ultimately if you have access to do something in a project, it applies to all issue types.
-
So your board filter is not including them. You'll need to adjust it so that it pulls them in.
-
You will need to keep the Epics in a separate project if you want to restrict access to them to a set of people.
-
Required version of what? A Jira upgrade from 7.3 to 7.4 won't throw any version errors.
-
You have used the wrong type of field. It's a common error. A "Message Custom Field (for view)" appears when you're on the issue view. The "Message Custom Field (for edit)" appears when you are on a screen with editable fields (create, edit and transition) Try the edit version of the field.
-
If the url you intend to reach gives you data, but your curl does not, then there's something wrong in the curl invocation. My guess is that your code is not expanding the $net and/or $issueid variables in the way you expect. You have not given the context of where that line is running. Maybe show us the script it is in?
-
Put some text in between <a> and </a> But, your html is broken - the <a part is not terminated correctly.
-
You have not told us what the problem is. For example: Are you getting some form of error? Is your browser just trying to connect and getting nothing, so you get a spinning icon and no response? Do you get a login or warning screen?
-
It took me a while to spot it! I was just fiddling with a REST interface and tried one of your calls which worked fine with localhost. Did it three times before noticing!
-
Mmm, you appear to be using Jira REST urls to contact a Confluence system... For Confluence, try /rest/api/content For Jira, your REST urls look right, except for starting with Confluence.
-
The REST API respects your screen setup. It can only amend fields that are on the screen, but it will only require fields to be set if they are mandatory during the transition.
-
The problem you have is that versions are different by project. Even if they have the same name, each one is a project/version pair with a different unique id in the database. The only work-around I've seen is a listener that can populate a select list which contains all versions. IT's not that easy to code either.
-
Well, you should use the right version of Java. Then you'll need to fix the connection timeout. I can't tell you what you've got wrong there.
-
That's only one way to do it. That's the point, it's just one approach. Some people want chunking, some need additions, some want other schemes.
-
I suspect this is more a case of you persuading Prolexic that you are not a threat. They're not just protecting Atlassian. However, if you want the official line from Atlassian, raise a support call with them over at https://support.atlassian.com/contact We're end users like yourself, we can't help you with systems we have…
-
Well, you can try it - a space export can work when imported on a much later version. The official way to do it, which will work, is to take a copy of your 4.2 system (or just the space), stick it into a dev system on 4.2, upgrade it to 6.3, then export from there and you'll be able to get it into the 6.3 production.
-
Tempo timesheets allows you to categorise your worklogs. There may be other add-ons, but most people I've worked with start with Tempo
-
Probably to contact support!
-
Sorry, I assumed you knew enough xml to spot it. It's most of a comment enclosure, but it's missing a shriek. Have a look up the file for other examples.
-
If it doesn't install when you ask it to, then it will be telling you why in the logs.
-
Ok, you'll need to look through the rest of the logs for warnings and errors. What is showing in the "manage applications" though? Just "not installed"?