Comments
-
The upgrade process covers all the elements you are asking about. Start at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
That's the whole point of this conversation - you can't move between status that are in the same column.
-
Edit the workflow, add status (and transitions into them) then map them into the columns in board configuration.
-
Sorry, I was slightly wrong there. Not sure exactly when it changed, but later versions of Jira do allow you to do a "full" edit on a workflow that has no issues associated with it. It used to be that if it were used in at least one workflow scheme that was active in a project (in 6.2 which is the only one I have to hand),…
-
Nice idea, but it doesn't give you HA. If one node fails, your users have to know to manually switch to the other, and your data goes out of sync.
-
They don't "look like duplicates" - a duplicate would mean two fields that contain potentially different data. They are aliases - one field with two or more names. The reason they exist is partially because some developers thought it might be good to allow them to use the fields internal name, and partly because users were…
-
The release note function in Jira was written to be quite simple (because everyone has very different needs from it) and output something designed to be copied and pasted into other systems to be tidied up before publication. Confluence would be a good choice for that.
-
Give the Docs team a chance to catch up - 7.7 can't do this, 7.8 does.
-
The "devil is in the detail" here. On step 3 - there is no simple "edit the workflow". Did it go into "draft" mode?
-
I know of a few ways to do this, but none I'd say were "good". Could you tell us how you are doing it, and what version of Jira it is?
-
No, scripted fields are updated at a lot of other times. It's an oversimplification, but you can almost always assume a scripted field is updated when the issue is indexed. Transition, comment, edit, move, etc.
-
Start with the help docs the message points you to. (Although 90% of the time, you probably want to check the disk the index is on looks healthy and then do a full locking re-index)
-
I'm that good. ;-) No, not in the slightest really. I just have accumulated notes. Resetting a password the hard way is something I've done a lot, so I've noted the salt and hash for "sphere" in several places.
-
Oh, I hadn't realised you're on such an old one. That's pre-crowd, so I'm not surprised there's no CWD tables now. Try this instead: update userbase set password_hash='uQieO/1CGMUIXXftw3ynrsaYLShI+GTcPS4LdUGWbIusFvHPfUzD7CZvms6yMMvA8I7FViHVEqr6Mj4pCLKAFQ==' where username='XXXX'; Then log in using the password sphere
-
Project is irrelevant, it's the whole server. Start at https://confluence.atlassian.com/enterprise/high-availability-guide-for-jira-288657149.html
-
The order by clause has to be the last in the query. Label works the same way as other data like Project. Try "Label not in (x, y, z)"
-
They use whatever address you set them up with. Most of us use names rather than IP addresses, so it doesn't matter if the underlying IP address changes.
-
If the cwd tables don't exist, then there's no way you would get as far as a login page. I suspect your database is case sensitive, or you're looking in the wrong one.
-
No. The new Cloud layout will not make it to Server versions for quite a long time. I'm not sure this is actually a bad thing, given the number of people who really despise the Cloud layout (I'm an Atlassian fan-boy, and even I don't like it)
-
I did that the first time I saw workflow properties too. I was looking for much the same!
-
Server only so far
-
Install Stride and hook it up to Bitbucket. (Or, if you want a non-Cloud chat, Hipchat server)
-
Log in as an admin, go to admin -> custom fields -> Technology, and click "configure". You'll see the current list of options and can add more (or change them, or disable or even delete)
-
The lock is there to stop you breaking your system by removing the required flag. Please, don't do it. If you do, you will break Software in interesting ways.
-
There is no way you can do that. Jira doesn't track view-only access. You have no control over the user's email to see if they have opened a notification. And in both cases, you have no way to read their mind to see if they've actually read it at all. Have a think about the chain of communication, the best you can do is…
-
Oddly, I was asking the same recently - https://community.atlassian.com/t5/Jira-discussions/How-are-you-monitoring-your-Atlassian-stack/m-p/727529 For the anonymous access, yes, it's on the "managing permissions" docs, but there's a lot there. The short answer is: * Log in as a Jira or System admin * Go find a project you…
-
Message?
-
You don't. The "locked" next to the field means you cannot change them. There are ways to unlock fields in the database. But don't. There's a good reason they are locked. In the case of Epic Name, chunks of Jira Software stop working if the field is left empty, so it's a spectacularly bad thing to do.
-
It is telling you what it is doing. "Extracting files" means it is unpacking the distribution. You'll find it moves on to starting the system up and then upgrading data and so on. With messages on screen to tell you.
-
You can't do it by issue type directly, the permission is a project one. In theory, you can though - if you have one workflow as you do now, copy it, and then add "workflow properties" to each status that block all but the project lead. However, think it through - if a user can prioritise ABC-123 (bug) but not ABC-456…