Comments
-
I hacked the .vm file that shows the groups in the sharing screen, so it never presented the jira-users and other groups people had been spamming with!
-
Ah, that's the new "user can create projects" function. Projects created by users can't have schemes applied to them.
-
Just what I needed, but annoyingly, it just confirms that you have not done anything wrong, and I suspect you've run into a bug. You'll need to talk to Atlassian support - https://support.atlassian.com/contact
-
There is a trick that requires no support type access. Create a simple CSV file with one column (filled with unique ids - numbers are easiest) and a number of rows equivalent to the issues you want to skip. Import it into the project, then delete the issues. This will clock the number up to where you want to start.
-
That's not "advanced", its "more fields". You'd need to hack the core code of Jira to move fields out of "more" and on to the main part of the simple search options.
-
One extra point that previous answers miss - you also need to think about moved issues. Imagine you've got project ABC, issues 1 to 60. If you move ABC-42 to project DEF and it becomes DEF-123, then perform one of the above, you're going to have problems when re-using ABC as a new project code when the new ABC-42 is…
-
I didn't have time to have a heart attack - I was stuck on a train heading into the office when I got the call. I was able to diagnose it within seconds as well!
-
Yes, that's correct. Default values are there for pre-filling fields during issue creation. The existing issues you have are already created, so they don't need defaults. If you want to change them, you'll need to (bulk) edit the issues to add the values you want.
-
My biggest mistake was also my smallest! In the days we did DevOps without calling it that, I looked after a small trading system and its test copies. A script I'd made a mistake in ran on schedule and over-wrote production data with an older version. Biggest mistake - it wiped £40 Billion (yes, billion) off the market…
-
You will need to explain "can't login" properly. What exactly are you doing?
-
Yes, we dumped it because it can all be done in ScriptRunner far more easily. See https://marketplace.atlassian.com/plugins/com.adaptavist.confluence.sr-notifications/server/overview
-
You have used the "field configuration" to set the resolution as mandatory, but not put it on the "create" or "edit" screens. Change the field configuration, make the resolution optional.
-
Yes it could be memory, as described in the docs we've pointed you to (it might not be memory, but we can't know until you have gone through the docs)
-
It's not an option any more. You are stuck with it. Sorry I can't do anything about it.
-
There are a couple of fallacies here: * Boards are not issue containers, they are views that select things you choose to see. "Move issue to board" is nonsense, as they're not containers. * A sub-task is part of an issue. An issue is contained in a project. It does not make sense to say that a sub-task is in a different…
-
The procedure for this is complex. Go to your Atlassian account and find the "download source" option. Download the code, hack it to amend the view screen, recompile it and then deploy the results.
-
@nigelb14- I am sorry about the previous comment. I've left it there so people can see why I'm apologising. I've just re-read it and it came out wrong. I think when I wrote "try again", I was thinking completely wrong, and I really should have explained what I really was thinking and in a way that comes across in a better…
-
Jira Software is pretty much built for supporting Scrum, so there's not really a lot of question on whether it's the right thing for you. "So far I think that the best practice for us would be to give our customers a user account for Jira software. That way they can see the progress of current sprints, define new entries…
-
I am not sure what the requirement is here, I am confused. You appear to be trying to restrict the resolution to certain entries depending on status, but then using a post-function to set it to something. Those two things don't really mix, they're different parts of the process. I can't see if you mean you want to stop…
-
The error shown here is too generic and short to tell us much. Could you take a look at the application log? It will have the same error in it at the same time, but you'll want to read all the "caused by" stuff below this current error.
-
You're right, if you can transition an issue from the issue view, then run a search for it and try bulk-edit on just that one issue, and it does not offer the transition rights, then there's something broken. The problem for me is that I've only once been able to get Jira to do that. I can either transition that one issue…
-
No, you don't need Core licences. There's probably several ways to think of this, but I like to describe it simply as "A Jira Software (or Jira Service Desk) licence includes a Core licence for the user". Technically speaking, you do have Core - it's the platform Software runs on top of. Your licence to use it is included…
-
There's no way to do this, unless you were to build a project that has one issue type per workflow, and allow everyone to use "view workflow" on a set of single issues in it, Your best option is to document your workflows externally. Most of us probably use Confluence to do that (I cheat a bit more and use scripts that my…
-
You don't need to be an admin. The "source data" is the issue history for the issues included, which can be seen by anyone who can see the issues.
-
The issue view screen is somewhat strict when it comes to layout. It deliberately gathers some types of similar/related data into panels so that users know where to look when they know what type of data they are looking for. Dates go into one panel, work records another, people and groups into a third, attachments,…
-
Yes. The data for the gadget is the list of issues it is configured to report on. The gadget looks at the issue history (available over REST) to do the calculations for the report.
-
This is your configuration, not the new view. You need to talk to your administrators and make sure that the assignee and story point fields are on the issue type's edit screen, and that you have the permission "assign issue"
-
I think you have misunderstood the problem on the question you have linked to, although I would say that the original question is very unclear. In that question, Joe was trying to get many bits of one page drawn into another. To do that, you need the multi-excerpt macro add-on. The part of the question you quote however is…
-
Those phrases are not useful as issue types, they show the status of a task. To use them, just create a project using one of the default templates, and it will build you a workflow with them.
-
A lot of us put a link to a Confluence page in the text, and/or use the description for some data, but it's not very visible. If you were on Server, there's an add-on called Profields that adds project attributes quite nicely too.