Comments
-
Do you mean tables and fields you place in your content? Or do you mean in the database? (which is really not a great place to do reporting from in Atlassian applications!) Best though - if you can describe what information you really want, we can probably tell you the best way to get it!
-
If she'd "nailed it", she'd have grasped why it's nonsense to do that.
-
Ah. Then no. And that's going to make a mess of your numbers if you try it in the database without updating other tables. It sounds to me like you've come up with some very poor scheme for achieving some perceived need that doesn't sound right to me.
-
Write and maintain in one place, see it in many (the include macros are a firm favourite in my usage) Use as a knowledge base in a help desk, with articles popping up in SD for users Massive extensibility Create many Jira issues directly from lines in Confluence Mention your friends to get them to help you with your pages,…
-
Browser was my next step after a "return to login". Well spotted!
-
Correct, none of the audit actions are retrospective, as there's nothing recorded until they are enabled.
-
That's not quite the right explanation. Transitions are NOT Status. The names of status and the names of transitions are totally separate things. Most of the project templates create workflows where they name a transition after the target status at the end of the transition. The button for a transition draws its name from…
-
I don't see any reason not to.
-
Check cwd_membership, after looking at your application permissions (that will tell you what group(s) have Jira-software-users)
-
I've set up most of an Atlassian stack with Let's Encrypt recently. You really can just follow the docs, and it's free.
-
Not change it, but you can set it. You've said you are inserting issues which is effectively "create" where you can set it.
-
Actually, Jira needs 768Mb RAM - that's the off-the-shelf default. If you've not messed with that, it is aimed mostly at getting started, and I usually increase it to 1Gb reflexively. Before going higher, you should know that RAM is a constraint, not just guess, or you'll just be giving yourself potential other problems.…
-
"integrate" is a "suitcase word", and hence pretty much useless in this question. You need to look inside it to find out what is really in there, then you can start to look at solutions. The obvious one is likely to be…
-
You will need to write an add-on that provides the field for that. Start at https://developer.atlassian.com/server/jira/platform/creating-a-custom-field-type/ (assuming you are on Server, not Cloud)
-
As an admin, go into the create screen again, and use the "configure fields" - you should see "where's my field" as an option. This is really helpful, as it lists all the reasons your field might not be there, highlights any of the ones that are blocking it and links directly to where you can fix it!
-
Accepting a password means it's getting you something. Could you describe what "not going to JIRA inside" really means? What do you see on screen? Also, what does the log say the problem is?
-
You can share the user directories with LDAP, but in this arrangement, you will need two Jira licences, one for each Jira system. But you don't have to have both sets of users on both servers. If you have two groups in LDAP, such as EU-users and US-users, then you only allow each group to log into their local server, and…
-
You could use Bamboo with a good naming scheme so that users aren't tempted, but it won't stop them adding their own with letters in them. Another thought sprang to mind for me - if you're willing to code (or use ScriptRunner), you could write a listener that picks up "version created" events, and does something with them.…
-
Are you Cloud or Server? I ask because Server scripts should let you set fields that are not on screen (and do scripted fields which also don't have to appear on screen, and could do the calculation based on the history instead of updates)
-
Yes. If you run a search for the issues you want to move, and get the list, you should find an option to "bulk edit" in the tools drop-down to the top right of the issue navigator (the list of issues) That option will ask you what you want to do with the issues, and you should find that "move" is one of those options. That…
-
There is no way to do this natively, I'm afraid. You could try injecting javascript to try to stop people using non-numeric characters, but you may need to make it work in many places, and javascript is notoriously hard to make work in Jira and hard to maintain or upgrade.
-
Yes you can. As I said before: Note, I've said "Task" here - that assumes you have an issue type called "Task", it is a sub-task-type, and you add it to your project issue-type scheme
-
It doesn't matter, it's only a warning, although it might be hinting that you've already tried to do something with your old data. I would concentrate on your original question. You need to get that backup working with an old install of 5.0.1 so you can upgrade it.
-
I don't think the Bob Swift one does that, no. Try the others I suggested.
-
The end of life error is a warning, telling you that your version is out of support. You can ignore it. Your process must be to create an old version of Confluence, the same as the version that was backed up, and restore your backup into it. You then need to step through the version upgrades recommended in the docs Ann…
-
I think you are in the wrong place. This is a place for people to talk about Atlassian and their applications. I think you might want to go to an Android Developer's forum?
-
No, the Jira service/process must not be running at all. It has to be completely shut down. You can do this in the API, you'll need to write code in an add-on to do it.
-
What is the trigger for this assignment? Is it on an issue edit? Creating the issue? Or is it randomly happening because it's 4pm on a Tuesday (i.e. your users don't seem to be triggering it at all)
-
With plain Jira, you're a little stuck if you want to split up the story like that. Best you can do is use sub-tasks with indicative summaries: (Note, I've said "Task" here - that assumes you have an issue type called "Task", it is a sub-task-type, and you add it to your project issue-type scheme) Story: Registration *…
-
Only by giving them a dedicated project with that one issue type available. You'll find plenty of other questions like this scattered around the community, with good attempts at it, but most of them are only partial workarounds and most can be broken or don't quite do what you need. Javascript used to remove options from…