Comments
-
Ok, but you have admin already, so you can just change the permissions on the space.
-
Ok, step back. What are you trying to do? If you are the admin, you're already in the group.
-
I took it from your code in the question.
-
You need an existing admin to add you to the group.
-
The only way I can get that to happen is with priority schemes (which you don't have implemented in this version, I believe) and javascript hacks that reduce the list of priorities. Can you try JQL search for "priority = x" and try putting in 1, 2 or 3 for x - does that complete the clause ok? And does the JQL query…
-
You could have one workflow with two transitions. One would have the screen with 5 fields on it and a scripted condition for "issue type != management" and the other have the 3 field screen and a condition for "issue type = management". But you'd need code for that.
-
Depends on where and why you're trying to do it. Why do you need to differentiate between them? Why does it matter in whatever you are trying to achieve?
-
The ability to change is also dependent on having the same field configuration for both issue types, as well as workflow.
-
This sounds like you want to report on information that you are not putting into Jira. If there's no start/stop or work logging going on, then Jira simply does not have the data for you to report on. I think you need to explain what data you ARE adding into Jira that you want to report on, then we can probably help you…
-
I've found videos are of very little use for training admins in my experience - I've taken new admins through various types of course and found that watching sets of long videos tends to teach them nothing. Have a read through https://confluence.atlassian.com/get-started-with-jira-software as a starter, alongside actually…
-
Ok. * What is the end goal? * Why do you think you need to reduce the numbers? * Why does the customer think they want this?
-
Ok. There's no direct impact of increasing the number alone to 100. But if someone uses it (adds more than 25 gadgets to a dashboard), then yes, you could well see noticeable performance issues. When a dashboard is rendered, it effectively makes a set of calls to the Jira API all the same time. Some gadgets are very simple…
-
The fix was to amend the permissions to allow the user to delete issues in that project (generally a bad idea, as people often delete stuff they don't want to, and it's a nightmare to fix their mistakes)
-
The answer is in the question really. * We have created a global field ... we intentionally did not added this field to any screen * Now since the field is not associated with any screen so it is not returned from API * ... the problem is the response of above /field query does not include information like which field…
-
Nope. The customer rarely knows what they really want. They often tell you stuff that is totally wrong. A good service provider will check that the customer really wants. So. * What is the end goal? * You've said "in order to reduce the number of request from Jira while auto-assignment", which begs the questions* What…
-
That's not a crash report, just a warning about a broken link. If that genuinely is the last thing in the log before Jira halts, then it's not a problem with Jira. It could still be Tomcat that is failing - what is in the log at the time of a crash for Tomcat? (Catalina.out)
-
You will need to find or write some code to do this. Something like ScriptRunner will enable you to create a post-function or listener that can read the estimate and calculate an end date. However, I would question why. An estimate is a measure of amount of work, not elapsed time. That's why the estimate is separate from…
-
No. You cannot do this in a post function, as you need the issue to not be in the middle of a transition. Moving an issue is complex whenever you do it. The project (and issue type) define ALL the configuration for an issue, and to avoid breaking your data, Jira checks compatibility when you do a move. What happens when…
-
But now you don't know who it is assigned to. Worse, it's assigned to no real person, so you don't know who is responsible for it. Really, this is a very bad idea.
-
A computer runs some code that makes it work. Ta-da!
-
I'm using lots of instances, Cloud, Server and Data Centre. Not sure what my systems have to do with your question though. I mention installation because your question is about using a macro that needs to be installed on a system if you want to use it.
-
Do you mean the size of the display, or the number of gadgets?
-
But it can be very useful to see how long it might take.
-
Atlassian's Portfolio team has put a lot of work into making it recognise Scrum data recently. However, it really does not depend on Scrum. Portfolio is most interested in your plain Jira issues. Kanban adds a couple of useful things related to working in a Kanban style, and Scurm adds some Scrum stuff. But Portfolio works…
-
Yes, adding new macros is an admin thing - they either need to install the add-ons that provide the macro, or write the user macro (or, in my case, copy and paste someone else's code)
-
Two options, if you want to avoid code and add-ons 1. Hack your database, setting the pcounter field on the table "project" to where you want to start for any given project 2. Preload and delete (create a csv file with 1000 issues, import it into the project until you reach your starting number, then delete the lot)
-
So, you have not added it to your Cloud system then.
-
You're biased! Just because the majority of the good user macros I run into are the ones you wrote, and half the rest are ones I wrote based on yours... Oh.
-
You're posting on a quite old and certainly out-of-date thread. I suspect you are simply looking at the wrong thing. All that matters to a Scrum board is the status. An issue is not finished unless it's in the far right-hand column on the board. That's it. Category, Resolution, even status don't matter. It just needs to be…
-
Because you've not added it to your installation?