Global update to Apps Script issues severity in tracker

[Andrew Roberts]

What's this all about then...?

A lot of my starred issues, e.g. this one, have been changed to either S1 or S0 which, if the order is the same as priority,  means they have been upgraded. Guess I can't complain about that, but I wonder what triggered it???

[DimuDesigns]

You are not alone. I've also noticed a sharp uptick of status/severity changes for Apps Script related issues over the last few weeks. It looks like Google's team is doing a broad/rough pass over the massive backlog of issues, updating the status of those that they deem infeasible or not. Issues that are tagged S0 probably won't be implemented or fixed. And S1 status looks like the issue is still open but not a high priority.

 
Check out this issue I reported back in 2017:
https://issuetracker.google.com/issues/67764685

It's a feature request for access to request headers in doPost() triggers. It has over 200 +1s, but Google decided not to implement it due to security concerns and the thread is now locked as of September 19th 2023 so it can't be +1'd anymore (which was followed with a status change from S1 to S0).

Maybe Google is just cleaning house and tiding things up a bit.

[Andrew Roberts]

That makes sense. So disagreeing with this: low numbers mean low priority/severity.  So it's a general downgrading of issues :(

But then the "web app banner" issue that has been the talk of the town and was fixed straight away is also a P1/S0. 

Confused.com :?

--
You received this message because you are subscribed to a topic in the Google Groups "Google Apps Script Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-apps-script-community/3OMzoezM-qM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/35f1cf06-9816-406c-a8e7-434381050db0n%40googlegroups.com.

[cbmserv...@gmail.com]

Usually a low number means higher priority. Their numbering seems to start with 0 and on to 1, 2, 3, .. Not sure how low they can go after 3.

 

S0 would mean it has the highest severity possible in the ranking  While P1 means it is high priority but not the highest (P0 would be highest).

 

I have also seen my issues get re-ranked lately which lends credit to Google wishing to re-prioritize the issues for handling. Unfortunately some of the issues opened have also been lowered in priority. Like this one which is now an S3: https://issuetracker.google.com/issues/167800880

 

I guess they view deleting a calendar event and not sending notifications when the event is deleted as no big deal.

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CAN1QPJR9iyjd8yG5dRZq2ush7PqqdX2%3DQwjjiUWJWZQh2SvxJw%40mail.gmail.com.

[DimuDesigns]

Hmm...then going by that logic S0 should represent the highest severity...so now I'm a bit confused by Google's messaging. My issue was flagged as infeasible, and then a day or so later severity went from S1 to S0. How does that make sense?

[CBMServices Web]

They may have discovered a much bigger problem related to this than they initially suspected.

Hard to tell. I wish they put a comment on why they changed priority or severity.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/58f6fc0a-57bd-4ea4-96a1-08627cdec773n%40googlegroups.com.