three different projects very confusing


I have been playing around with Jira for the past few days. I have created some issues and done some searches and created some saved filters.

Overall, I like Jira's interface. There are some rough spots like unnecessary fields on the create issue.

But by far the most confusing part is the three different buckets of issues: feedback, backlog, and development. Actually, if feedback, backlog, and development where three different views into the same bucket of issues, then I dont' think there would be any issues. That's how I thought it worked.

I had created several new isseus in feedback, if I then clicked Preset Filter->Reported by me, it would show all the issues I created.

I came back the next day and clicked Filter->Reported by me, and there was nothing. NOTHING!

That's when I realized the issues must be getting moved around from feedback to backlog to development? I now had to goto the development project and click Filter->Reported by me, to see my issues.

For me, that is the most annoying part (by far) of jira so far.

I don't see why JetBrains didn't use a single project and have 'feedback'/'backlog'/'development' be a custom field which default to 'feedback'.

4 comments
Comment actions Permalink

Oops. I meant to post this under "JIRA: Help us help you."

0
Comment actions Permalink

Ok! It was very long thread even for Jive and NNTP, let's start new.

1. If Jira will have category of projects as search term or even hack for this by enumerating interested projects in the URL of saved filter it will be easier.
2. Time for JB to provide saved filters for most whinning part of community :)
3. For users that interested only in IDEA projects it would be good to make separate user group with access only for IDEADEV, IDEA and IDEABKL projects.

One more time:
IMHO previous tracker was good for posting and it was more forum- not traker- like last time.
JB was lost in all this info and Jira it's try to take control back.

TIA,
Dmitry

0
Comment actions Permalink

Alex wrote:

I don't see why JetBrains didn't use a single project and have 'feedback'/'backlog'/'development' be a custom field which default to 'feedback'.


I think the main reason was to have different access control for
different users in different projects.

--
Rob Harwood
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Rob Harwood (JetBrains) <rob.harwood@jetbrains.com> wrote:

I think the main reason was to have different access control for
different users in different projects.


Isn't that what setting up multiple usergroups would do? i.e. in my jira
install we have a "staff/developers" group, "staff/support" group, and
others.

Different projects have different access rights depending on the group of
the user - i.e. developers can't resolve support issues.

The problem I have with our install is theres no granularity (sp?) at the
issue level, so I can't say "only staff see issues FFF-05, FFF-06, and
FFF-110, but all "publicusers" see the rest. This functionality is
however available in the enterprise version I understand.

Would this functionality provide the different ACL access JetBrains want?

Mark

0

Please sign in to leave a comment.