How are priorities assigned on Jira ?

[Miykichii]

I came across this ticket on Jira, while still waiting for Sebastiano to reply back, however he said in a different ticket (my Members List Ticket) that request improvements are counted Trivial even though in the past i had view that were marked Major. This ticket is different though, I think this ticket should be set to Major as it doesn't contain simple restyling but a set of important features.

http://tracker.vbulletin.com/browse/VBV-12665

Original size http://i.imgur.com/TJKDcUP.png

[TLMD]

I guess for improvement requests it is difficult to get a "major" tag, since mostly they are not about a "major loss of function", but about new features.

If you click the questionsmark next to the dropdown menu, you can get an idea about the priority levels:

[Miykichii]

I guess for improvement requests it is difficult to get a "major" tag, since mostly they are not about a "major loss of function", but about new features.

If you click the questionsmark next to the dropdown menu, you can get an idea about the priority levels:

[ATTACH]n4044617[/ATTACH]

Well based on this chart, definitely this ticket is not a Trivial issue, this ticket about Profile Media Tab isn't cosmetic misspelling or minor change - it has a whole set of unique and i think complex features to manage.

[Wayne Luke]

It isn't a major loss of functionality because it doesn't exist so it isn't major. It doesn't prevent the software from working or cause data loss so it isn't critical. It doesn't prevent development or QA testing so it isn't a showstopper.

Priority isn't the only thing that ranks issues though. During bug reviews, it will be assigned a visibility which can be ranked from 0 (implement as quickly as possible) to 5 (only impacts a small number of users). This gets multiplied by the priority to determine the order issues are worked on within a version. For improvement requests they also have to get a number of votes and we try to work off things based on the Issue Rank (priority X visibility) and then votes for improvement requests. Things aren't perfect and sometimes something can't be put into a two-week work period so it will get delayed but it is the system in place currently.

As for the trivial, you can probably do most of what you want via css_additional.css to customize the page and make it work the way you want.

[Miykichii]

It isn't a major loss of functionality because it doesn't exist so it isn't major. It doesn't prevent the software from working or cause data loss so it isn't critical. It doesn't prevent development or QA testing so it isn't a showstopper.

Priority isn't the only thing that ranks issues though. During bug reviews, it will be assigned a visibility which can be ranked from 0 (implement as quickly as possible) to 5 (only impacts a small number of users). This gets multiplied by the priority to determine the order issues are worked on within a version. For improvement requests they also have to get a number of votes and we try to work off things based on the Issue Rank (priority X visibility) and then votes for improvement requests. Things aren't perfect and sometimes something can't be put into a two-week work period so it will get delayed but it is the system in place currently.

As for the trivial, you can probably do most of what you want via css_additional.css to customize the page and make it work the way you want.

Well, i've simplified the Jira ticket that way it does indeed match the priority as trivial. I think this priority process is like a hit and miss based on opinions.

[Miykichii]

It isn't a major loss of functionality because it doesn't exist so it isn't major. It doesn't prevent the software from working or cause data loss so it isn't critical. It doesn't prevent development or QA testing so it isn't a showstopper.

Priority isn't the only thing that ranks issues though. During bug reviews, it will be assigned a visibility which can be ranked from 0 (implement as quickly as possible) to 5 (only impacts a small number of users). This gets multiplied by the priority to determine the order issues are worked on within a version. For improvement requests they also have to get a number of votes and we try to work off things based on the Issue Rank (priority X visibility) and then votes for improvement requests. Things aren't perfect and sometimes something can't be put into a two-week work period so it will get delayed but it is the system in place currently.

As for the trivial, you can probably do most of what you want via css_additional.css to customize the page and make it work the way you want.

Wayne, you've just marked my new ticket on Jira Trivial. If i find my efforts aren't appreciated, i am not going to participate further as it will be considered a waste of my time and you're killing motivation with these actions. Your action offends me even after reading this topic because you understand that these set of features isn't a trivial change. This new ticket is related to a set of new features.

http://tracker.vbulletin.com/browse/VBV-12676

This is about the community and Vbulletin. I mean if you think this is trival then i think many of your tickets that are marked minor or major are also trivial. Like i said, the system isn't perfect and appears to be based on the staff personal opinion. I really don't like this in particular. Keep the good members participating rather than degrading participation.

You might as well go ahead and change all these priority from major to trivial as well. They are all set to major and approved for major.

http://tracker.vbulletin.com/browse/VBV-12406 (Blog redesign)
http://tracker.vbulletin.com/browse/VBV-12337 (Discovery a whole new set of features - Feeds)
http://tracker.vbulletin.com/browse/VBV-12379 (Group redesign)

I don't understand why Vb staff can't re-edit their position when taken. This media tab ticket should be marked a Major because it is not a trivial issue that can be at the bottom of the list. There is a reason why this list of definition is in place.



VB 5.x is still in beta and it needs to be rebuilt well, unless these functions/features are hard for VB dev to code that is why they marked it Trivial to ignore it, that would be another story.

[Wayne Luke]

It hasn't been reviewed by the bug review board yet. This issue is about some CSS changes. The others require rewriting code. There is a big difference. Your suggestions and contributions are appreciated. However there is red tape that must be gotten through. Nonetheless Priority isn't used in a vacuum and a higher priority won't get your suggestions implemented sooner by itself.

You should campaign for votes on your improvement request issues if you want them looked at quicker. They need to appear on this page here:

http://tracker.vbulletin.com/browse/VBV#selectedTab=com.atlassian.jira.plugin.system.project%3Apopularissues-panel

[Miykichii]

It hasn't been reviewed by the bug review board yet. This issue is about some CSS changes. The others require rewriting code. There is a big difference. Your suggestions and contributions are appreciated. However there is red tape that must be gotten through. Nonetheless Priority isn't used in a vacuum and a higher priority won't get your suggestions implemented sooner by itself.

You should campaign for votes on your improvement request issues if you want them looked at quicker. They need to appear on this page here:
http://tracker.vbulletin.com/browse/...arissues-panel

Thanks... well i know these features will take time to implement + if they are marked Trivial in the statistics report they will be treated as trivial issues when they should be one of the main priority features. I mean we don't want to keep further implement features in the wrong approach and later find that we need to scrape them to re-add a new set of better features, when that point is reached, it becomes nuisance for the developers to address such issues, at least in my opinion.

If you can please marked it as 'Major' and wait for a VB developer to review it and change the priority himself, I would appreciate it. I hope you understand what i mean.

http://tracker.vbulletin.com/browse/VBV-12665

[Wayne Luke]

When choosing what to implement, they don't look at the priority first. They use the Issue Rank. A trivial item can have a higher issue rank than a major item. So I wouldn't place too much attention on the priority overall.

[Miykichii]

Edit : nvm