Comments
-
Just to expand on that - there's no need to set the value of a scripted field. The script does it all. The values are calculated by the script whenever the issue is re-indexed (that's not strictly the way it works technically, but it is the easiest way to think of them working)
-
Have you added the "time tracking" field to the issue create and edit screens? Also, do your users have the permission to "log work"
-
Hmm, I can't replicate this. Are you on server or cloud?
-
Oops, yes, I forgot which versions were pulled around then. You should not be using this version at all, but if you need the download for building a test rig for your upgrade testing, you can try contacting Atlassian for a copy. https://support.atlassian.com/contact
-
Go to the download page, and click on "all server versions", then look for "view all versions"
-
Ahh, well spotted! Another thing in the new view that's broken. It's not even ready to beta I reckon!
-
If you don't know what the address leads to (because you have no DNS entry for it), then there's no way the computer will be able to find it. It will work locally when you use the local address (localhost) You could spike the hosts file with a hard-wired address if you want, but that will still only work for that one…
-
Usually, because it's still starting, or has failed. Read the <jira home>/logs/atlassian-jira.log to find out what the problem is.
-
Do you have create and edit issue permission in the project? (Remember admin rights are not project rights)
-
A simple trick would be to find or write a post-function that, when a "close subtask" transition is done, looks at the parent issue and creates a new subtask on it.
-
Correct, yes. You need to run Server on something that you control the cname for. (Or get a hosting company to run Server for you)
-
Adaptavist is not Atlassian, and we have a different approach. We're smaller, but much more focussed on the product, so when we have things in the backlog, we do get to them faster. The link Thanos gave you is for the issue in his teams backlog. If you would suggest a better system that does not come back to "just do…
-
Do you have edit and create permission in the project? (Admin rights are rightly separated from project permissions and irrelevant here)
-
Many of the solution partners do hosting (and to be open about it, that includes my lot, although I'm in a different division of the company). You'll find a range of levels from "we'll install and run it on our kit, handle backups etc, but you do all the admin" through to "we'll be your Confluence administrators"
-
Could you describe "can't select it" in more detail? What happens when you click?
-
Steven's answer is still correct at this time.
-
Ok, so to be clear, what you are seeing is: * You have two users, A and B. * A creates a new issue * There is no reporter field on screen for A * The issue is created, showing B as the reporter If that is the case, then you have a script or automation in a post-function that is changing the reporter field.
-
That script is for Jira 7+ Jira 6 has different user objects, you'll need to convert it to use applicationuser objects I think.
-
The big grey tick mark to the left of the answer.
-
1. Yes 2. Not without coding of some form. The reason screens were implemented was to allow for different fields to be presented at different places, as you're trying to do.
-
The easy solution is to remove the field (that you don't want on the create screen) from the create screen.
-
That's nothing like your original question. Now you are saying that the reporter of an issue has been changed after it was created. That's simple to work out how - look at the issue history, it will tell you when the reporter was changed, and by whom.
-
Add the reporter field to the create screen, and make sure the people creating the issue have the permission "change reporter"
-
The error message is telling you that Confluence cannot read the file from the attachments directory. You will need to look at the server to establish why it can't read it.
-
No, that would make tasks useless, so you can't do it.
-
You will need to write some code. The most simple approach is probably a listener that catches the "move issue" event and updates the issue's data afterwards.
-
Nope you're missing nothing, the boards are still not in Server, and might never make it.
-
You've checked the permission helper I guess? If so, then look at the properties on the status the issue is in.
-
If you want someone to do the install for you, you probably should go to one of the solution partners. See https://www.atlassian.com/partners/search
-
This is the wrong approach. Post-functions are too late. Write a validator instead. When the transition screen is given to the user, a validator will check whatever you need to check at the point they click the confirmation. If it fails the check, it will return the user to the transition screen. On the last click where…