Comments
-
Sounds like you have not added the field to the "dialogue". I'm not sure exactly what you mean by that though, but I think it's the "create" screen for the sub-task type.
-
Go to the issue type scheme for the project, and add a new issue type to it.
-
No, they selected a different type of sub-task. You can add as many different types as you want. Have a look at the issue type scheme for the project.
-
To be able to do something in bulk-edit, you have to be able to do it to the issues. You'll need to add the field to the screen before you can bulk-edit them.
-
All JIRA's data is in the database. I don't know what you mean by "logwork screen"
-
It still uses web-section and web-item. See https://developer.atlassian.com/jiradev/jira-platform/jira-architecture/web-fragments
-
JIRA does not have anything underneath sub-task, but if you do your test suite as a normal issue type, it will work fine for you.
-
It's worth training your users to *never* use browser links. They break if pages are moved or renamed and on migrations and creating test systems. You should *always* use internal links.
-
The concept of "core" only came in with JIRA 7. You say you're on JIRA 4. However, whatever version you are on, have a look in <jira installation>/bin for the startup files, and <jira home>/logs for the reasons why it might not be starting.
-
If the system is telling you that it can't complete the sprint, it will also be telling you why. What errors are you getting from it?
-
I've seen it in a couple of places, and the answer has always been: Use your user directory properly and set up a group for "can use JIRA" I've never been able to find any other work-arounds.
-
You would need to write some code in JIRA to poll your database for changes regularly, write a JIRA workflow trigger that could do the same, or get some database trigger to run something that can issue a "transition issue X" over JIRA's REST interface.
-
Hmm. I was able to download and install it. Is there something interrupting your downloads?
-
There's no public roadmap for these changes. There's some in JIRA 7.3 and 7.4 as I said, and I'd expect some more over the next few releases.
-
If this is Cloud, you'll need to raise it with https://support.atlassian.com If it's Server, then you'll probably need to check what has gone wrong with your add-on, checking log files and see if it's been upgraded and caused problems.
-
An importer is a block of code that can read and understand a data source (file, database connection, etc) and convert the incoming data into JIRA data. These data sources are almost always other issue trackers of some form. To add a new importer, a new add-on is required to implement the read-source-write-JIRA process. So…
-
You might want to explain what you're using to do this code, and which Atlassian application your add-on is for.
-
1. No. Not yet. Atlassian are moving that way (after 12 years of us whinging about it), with 7.3 introducing some limited workflow changes for project admins, and 7.4 some stuff with screens as well. 2. That's another layer, and it's not going to happen. The admin rights are going to stay at the project level, as that's…
-
This is a very common problem with JIRA. The default setup has a group that says "can log in". This is fine. It also goes on to use that group as a default for "can see project". This is not fine, because it leads us into exactly the problem you have - everyone can see everything by default. You need to look at all of the…
-
Absolutely not. Do NOT update the database in any way, you will break it. I don't recognise te app_user name for a table which makes it even worse, because it makes me think that you do not know anything about the way JIRA uses the database. Your description of the problem is good, but I think I might not be understanding…
-
Um, there's no way SSO can work that way. The whole point of it is that a person says "hey, it's me, <identifier>" and that identifier is recognised as a single identity. What you're doing is effectively randomising the identifier. There's no way a set of systems can recognise the same person from an unrelated set of…
-
I'm glad I got you to a solution. Looking back over the conversation, I was struggling to explain myself (I'm going to try to partially blame a long busy day), and I really think I wasn't translating my "how JIRA thinks" into "how it applies to Scrum" well at all. I should have realised that you get Agile a lot earlier and…
-
No. You mean board. Projects do not have a backlog. If you create a Scrum board that includes all the issues, you will find that the sprints clash, because you've got a board including more than one sprint. Either don't do that, or enable parallel sprints (see…
-
No. You're missing the point of Scrum. With a Scrum, you have a backlog of things that need doing. You break up your work into sprints (blocks of time) To start a sprint, you commit to doing a set of things in the backlog, and then start the sprint. You do not run more than one sprint off that backlog. That's the basics,…
-
No, I should have used a stronger word than "like". The use of components was an example. You could do it by issue type, custom field, date, anything. Your boards need to select different exclusive lists of issues.
-
Most modules can be made to do mail notifications. You need to be writing a module that can hook into the administration functions. I'm not sure that there is a specific type for that.
-
No, your *boards* need to select different issues. Like board 1 looks for "component = X" and board 2 is for "component = Y"
-
It's nothing to do with the project. You need your boards to select separate sets of issues.
-
Sprints do not belong to projects, they are associated with boards. If you have three boards looking at the same project, this will work fine, *but* you'll want to set up the boards so that they only look at the issues related to the team. Once you've got the hang of that, then you might want to look into enabling multiple…
-
Yes, it does, and then later, we delete the project to get rid of the issue data we don't need. This and the gui are the only ways to add at the moment.