Comments
-
So progress here is "Number of sub tasks complete / total number of sub-tasks". That should be quite easy to code for.
-
Percentage of what? What are you measuring when you say "progress"?
-
Labels on pages are global, not limited to spaces, so I'm not sure what the question is there. There are no restrictions on creating labels, but there are some neat add-ons in the marketplace (Labels cage is the one that springs to mind) which can help you either keep on top of labels or limit their scope and values. I'm…
-
You can't, directly. The point of the diagram is that it represents your process via the board, and the board should represent your process as built into the workflow. You've set it up not to. A solution would be to have a second board set up to match the workflow and use the CFD on that (and educate the users that the…
-
Looks fine to me. Possibly just a glitch?
-
The reason timesheet add-ons exist is because you can't do this in Jira off-the-shelf. Jira is issue-focussed, and there is time reporting in it, but you have to think in terms of issues rather than people. Run JQL for any issues your user may have logged time on, then use the timetracking reports and you'll be able to see…
-
"I tried the normal way" tells us nothing. What do you think "the normal way" is, what did you do, what did you expect, and what went wrong?
-
It's nonsense to use a field twice. If a user enters a summary at the top of the page and then another one in the middle, which one goes into the summary field? Jira stops you from repeating a field because it would confuse the users and force admins to have to think about which data to keep and which to ignore. I suspect…
-
Ouch. You need to move to MS SQL Server 2012 at least. 2008 simply doesn't work with Jira 7.2 upwards.
-
Changing the board estimation does not change the estimate field, it changes the field the board looks at for its estimates. You're not saying "change time tracking field to story points" (which would not work at all), you are saying "look at story points instead of time tracking when doing your work" If you want to use…
-
This does not make any sense. Update of what? What's 4.2? Time estimation in what? You have tagged this with Jira, but even assuming that, the words make no sense.
-
You'll need to explain where you are seeing this and what you're doing to provoke it.
-
No, there's no view function, it's all based on user permissions. I suspect your current approach is the only option.
-
See "customise fields on a request" in https://confluence.atlassian.com/servicedeskcloud/configuring-request-types-and-workflows-732528910.html
-
Go to your my.atlassian account, and look under your licence for "jira software". You can download the code from a link there.
-
There is no "conversion". You buy the new Cloud service and move your people over on to it. If you are within the first 30 days of your server licence, you can get a refund.
-
Greenhopper is the original name for what became the Agile add-on, which became the Jira Software application with Jira 7. "How to use it" is basically "write code for it", we can't really tell you more than that.
-
No, there's no simple way to hide this useful information.
-
You'll need to write code to do this. Specifically, a listener that can pick up all changes to sub-tasks and re-index a parent issue that has a scripted (calculated) field on it, or amend the custom field on the parent. I'd use the Script Runner add-on to do it, and have done in the past (But that's because I always have…
-
One way I keep running into this is a missing separator in the CSV. A field overflows by effectively concatenating the whole line (or even the rest of the file) into one field.
-
No problem, mistakes happen. If you do use Atlassian stuff, feel free to rejoin us here!
-
There is no error there?
-
What is on line 77 where the error happens? There's an "addUrl" call on line 3, but we have no way of knowing that this is where the error really happens. Please, give us the whole thing, NOT as a screenshot image, as those are useless for code, but the whole script (redact data if you need to, it's the structure and code…
-
No. The project and issue type are structural - they determine what fields appear below. It would not make sense to have any other fields in there, because they wouldn't have that effect. On the words used, yes, you can if you translate the system to another language, or edit the language pack currently in use.
-
Go to Admin -> Issues -> Screens and find the screen in use for your project and issue "create" process. You may find it more easily by going to the project you want to do this in, go to the admin section and look for the "issue type screen scheme" - you can descend into that, as it's a group of "screen schemes" which in…
-
Could you explain what this has to do with Atlassian products?
-
You don't. It's in the docs, but there's a lot to go through before you see it, so I'm not surprised you missed it. The results of these issueFunctions only exist in the issue navigator, they're not fields. However, as you have ScriptRunner, you can do it as a field. Write a scripted field that adds up the two numbers for…
-
No, that's fine, the indexing just needs to happen after the status, history and store actions. Email sends won't affect it, unless they're going wrong and stopping it getting to indexing. If unsure, move the indexing up above the emails.
-
Adding users is done in manage users, then you add them to the group.
-
Go to the project admin section of each project and read the permission scheme, looking for "administrate project". The rule in there should say something like "Role: Admins". Go to the people section of the project and add the group to the role. (If it's not role:Admins, you'll have to work out what to do from there)